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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Purposedifferent
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.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.For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.
Complexitydifferent
LowMediumHighHigh
Timedifferent
15-30 min1-3 h2-8 h1-6 Wochen
Participantsdifferent
2-63-102-84-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresProcess Map, Handoff List, Improvement BacklogProblem Analysis, Decision Analysis, Risk Plan8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
ProcessOperationsImprovement
Problem solvingRoot causeDecisionOperations
QualityProblem solvingRoot cause
Add more methods