Keep calm and use the runbook
cortex.io
Keep calm and use the runbook
1–10 of 51 posts
Re: Keep calm and use the runbook
#2This reminds me of the book The Checklist Manifesto and the show Air Crash Investigation.
Re: Keep calm and use the runbook
#3Runbooks the key ingredient to making any job unbearable. Sorta /s
Re: Keep calm and use the runbook
#4This reminds me of the book The Checklist Manifesto and the show Air Crash Investigation.
My first thought when I read the title was "Sounds a lot like the non-normal checklists they use in aviation" :D
Re: Keep calm and use the runbook
#5Runbooks the key ingredient to making any job unbearable. Sorta /s
So what's your experience with them?
Re: Keep calm and use the runbook
#6It is obvious to me that keeping the runbook up to date is really important. But how do you foster a culture in which everyone keeps it up to date?
Many people don't even read the readme, let alone correct it. Is it cultural? If you are so privileged that your books are updated, please share with us your ways!
Re: Keep calm and use the runbook
#7It is obvious to me that keeping the runbook up to date is really important. But how do you foster a culture in which everyone keeps it up to date? Many people don't even read the readme, let alone correct it. Is it cultural? If you are so privileged that your books are updated, please share with us your ways!
Round robin on-call
Re: Keep calm and use the runbook
#8It is obvious to me that keeping the runbook up to date is really important. But how do you foster a culture in which everyone keeps it up to date? Many people don't even read the readme, let alone correct it. Is it cultural? If you are so privileged that your books are updated, please share with us your ways!
Post mortems/RCAs with after action items (that get followed)
Re: Keep calm and use the runbook
#9It is obvious to me that keeping the runbook up to date is really important. But how do you foster a culture in which everyone keeps it up to date? Many people don't even read the readme, let alone correct it. Is it cultural? If you are so privileged that your books are updated, please share with us your ways!
It's cultural.
Many companies will block folks from releasing "incomplete" work, so you end up with either no runbooks, or "complete" runbooks that go out of date incredibly quickly.
Optimising for editing (https://onlineornot.com/incident-management/incident-respons...) helps.
Re: Keep calm and use the runbook
#10It is obvious to me that keeping the runbook up to date is really important. But how do you foster a culture in which everyone keeps it up to date? Many people don't even read the readme, let alone correct it. Is it cultural? If you are so privileged that your books are updated, please share with us your ways!
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.