methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.
Complexitydifferent
LowMediumMedium
Timedifferent
20-60 min1-3 hAs needed
Participantsdifferent
1-43-104-15
Formatdifferent
AsyncWorkshopWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathProcess Map, Handoff List, Improvement BacklogIncident Log, Action Tracker, Stakeholder Updates
Tags1 shared
OperationsReliabilityDocumentation
ProcessOperationsImprovement
IncidentOperationsReliability
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk