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
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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.For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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
LowLowMediumMedium
Timedifferent
20-60 min1 h bis mehrere Wochen45-90 minAs needed
Participantsdifferent
1-41-82-54-15
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeA3 Report, Action Plan, Root Cause AnalysisIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
OperationsReliabilityDocumentation
Continuous improvementLeanExperiments
LeanProblem solvingCoachingOperations
IncidentOperationsReliability
Add more methods