We learn a lot from our State of On-Call Report, which is one reason we keep doing it. Something we noticed in the 2015 survey was the prevalence of respondents saying that runbooks are one of, if not, the most valuable things to help solve problems faster.

It makes sense. When it’s 4am and you’re getting a critical alert from a service you don’t know much about, a runbook can provide the difference between fixing the problem in 30 minutes and taking 3 hours to resolve the incident.

Whether it was an anecdotal response or specifically related to a survey question, many on-call engineers are realizing (or remembering) the importance of runbooks.




We ran a series of blog posts last year (three in total), outlining what makes up a Minimum Viable Runbook and then explaining how to create one for yourself. In an effort to consolidate that knowledge and make life easier for you, we put all of that good stuff together into one place.

Introducing our new Guide to Minimum Viable Runbooks!



If you’re looking to level up your incident management strategy and get started using runbooks, this is a great primer. We break down what information you need to include in your Minimum Viable Runbook, why runbooks are important and a few suggestions of tools that can make the entire process easier.

What are you waiting for? You have runbooks to create, problems to solve and many other things to do. With this guide, we can help with the first two. Let us know what you think!