Yes its cultural, but you can change culture. Simple checklists that the team agrees upon for tasks that should be completed for a certain process. Just an exa

Yes its cultural, but you can change culture. Simple checklists that the team agrees upon for tasks that should be completed for a certain process. Just an example: after each incident do a postmortem, part of which is an update of runbooks and do a quick share in the team of those updates. Doesn't have to be bureaucratic and fancy, everything can be short and skipped when its really not relevant. But when everybody on the team agrees with them, and you have some sort of peer review baked in, it will be a lot easier. Because the same people who don't update the runbooks do actually feel it would be better if they did.