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 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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 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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowMediumHighMedium
Timedifferent
15-30 min1-3 h1-6 Wochen1-4 h
Participantsdifferent
2-63-104-103-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresProcess Map, Handoff List, Improvement Backlog8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
ProcessOperationsImprovement
QualityProblem solvingRoot cause
Root causeProblem solvingQualityIncident
Add more methods