Navigate Incident Management Like a Pro: MyFitnessPal's Sr. Director of Engineering Shares Insider Strategies with Lee Atchison
How much time are engineering teams spending on incidents?
Are you trying to set your engineering team free to do their best work? Read our new case study to learn how Blameless can help you do that.

Introducing Blameless Runbook Documentation

At Blameless, our mission is to provide teams with the tools they need to operationalize SRE and embrace a culture of resilience. We help teams automate toil and adopt best practices across integrated incident management, comprehensive retrospectives, service level objectives, reliability insights, and more. We are very excited to announce that teams now have a new tool in their tool belts with our latest launch. Blameless Runbook Documentation is now available for early access.

Runbooks are an industry best practice, empowering teams to codify the incident response process and drive process repeatability and consistency. Runbooks are sometimes called playbooks, with the choice of runbook vs playbook usually depending on the scope of the instructions. These sets of instructions allow teams to resolve incidents faster with greater confidence and less toil.

Below is a description of Runbook Documentation capabilities, as well as how you can get started with it today.

Documenting tasks and actions

Blameless Runbook Documentation allows users to create sets of documentable tasks and actions. These drag-and-drop tasks and actions can be in basic text, rich text, or code snippets. This allows for a more robust runbook with better context, as teams can include images, scripts to run, and more.

GIF of editing a runbook

Knowledge share and communication

Beyond helping teams resolve incidents faster with improved context and less cognitive overhead, Blameless Runbook Documentation also helps by centralizing critical documentation around operations. Information is now codified and available to all users within an organization. This limits tribal knowledge and helps engineers get onboarded much faster.

GIF of creating a runbook

Blameless Runbook Documentation also eliminates the need to store runbooks across various tools (wikis, Confluence, PDFs, etc.), which often increases cognitive overhead both during and after incidents. Instead, runbooks are all editable within Blameless and easily attachable to incidents.

Runbook Documentation helps teams see the gaps in their processes, as well. Teams can analyze runbook completion. Steps often skipped, ineffective, or that cause confusion can be revised. This gives teams the information necessary to refine runbooks.

Blameless Runbook Documentation provides a foundation for additional functionality that will allow teams to automate end-to-end incident workflows. In the future, customers will have access to out-of-the-box workflows across common tools to standardize incident communications, synchronization, and more.

Blameless Runbook Documentation is available for early access. To get started, fill out this form.

If you want to learn how Blameless can help your team adopt operations best practices that are specific to your business objectives, schedule a demo. 

For more information on runbook best practices, check out these resources:

Book a blameless demo
To view the calendar in full page view, click here.