Purpose
The method helps clarify workflows, data, causes, and improvements concretely. It identifies patterns, causes, bottlenecks, or constraints and derives actions. The outcome is captured as a runbook, checklist, and escalation path.
Operations
Runbook
Turns workflows, data, causes, and improvements into a tangible result by defining a scenario, writing steps, and testing and updating.
Which steps does a trained person execute in which order to handle the trigger safely without having to improvise?
LowAsync20-60 min
How it works
The team follows the steps: define a scenario, write steps, add checks and rollback actions, define escalation, and test and update. Each step is captured visibly. At the end, a runbook, checklist, and escalation path are available so decisions, tests, or actions can follow directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Define scenario
- 2Write steps
- 3Add checks and rollback
- 4Define escalation
- 5Test and update
The runsheet guides execution with 6 phases, timeboxes, 6 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- On-call Tasks
- Incident Response
- Repetitive Operations
Not good for
- Open discovery
- New strategic work
Deep dive
In detail
Runbook follows a clear working logic: define a scenario, write steps, add checks and rollback, define escalation, and test and update. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. As a result, a runbook, checklist, and escalation path support decisions, learning, or further planning.
Facilitation
Prepare a clear guiding question, the right information, and a visible workspace. Plan about 20-60 min with 1-4 people and use the format asynchronously. The facilitation stays lightweight; short timeboxes, visible intermediate results, and a parking lot for open questions help.
Output artifacts
RunbookChecklistEscalation Path
Artifact templates
Runbook ChecklistChecklist for operational runbooks with trigger, diagnosis, action, rollback, and escalation.checklist
Runbook ChecklistChecklist for operational runbooks with trigger, diagnosis, action, rollback, and escalation.
checklistrunbook-checklist.md
Checklist for operational runbooks with trigger, diagnosis, action, rollback, and escalation.
- Trigger described clearly
- Prerequisites and access listed
- Diagnosis steps in order
- Actions with expected effect
- Verification after each critical action
- Rollback or stop criterion
- Escalation path with contact
- Last test run documented
When to choose differently
Short decision aid for existing alternatives.
RAID Log
Statt Runbook, wenn du Risiken, Annahmen, Issues und Abhängigkeiten knapp im Projekt festhalten willst.
Similar methods
All methodsDevOps
Incident Command
Turns incident work, roles, and countermeasures into a tangible result by declaring an incident, assigning commander and roles, and closing and reviewing the incident.
Operations
ABC Analysis
Turns options, criteria, and risks into a tangible result by collecting items or causes, choosing a metric, and prioritizing top factors.
Operations
After-Action Review
Turns workflows, data, causes, and improvements into a tangible result through naming objectives, describing actual execution, and defining actions.
Operations
ALPEN Method
Turns workflow, data, causes, and improvements into a tangible result by listing tasks, estimating duration, and reviewing afterward.
Operations
Fishbone Diagram
Turns workflows, data, causes, and improvements into a tangible result by defining the problem, choosing cause categories, and prioritizing likely causes.
DevOps
Game Day
Turns incident work, roles, and countermeasures into a tangible result by selecting a scenario, preparing environment and rules, and improving runbooks.