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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitysame
LowLowLow
Timedifferent
20-60 min1 h bis mehrere Wochen15-30 min
Participantsdifferent
1-41-82-6
Formatdifferent
AsyncWorkshop + asyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeRoot cause notes, Countermeasures
Tagsno overlap
OperationsReliabilityDocumentation
Continuous improvementLeanExperiments
Root causeIncidentLeanProblem solving
Add more methods

Often compared together

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

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
Paper illustration for Kaizen Event.
Operations
Kaizen Event
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe