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
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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
LowLowHighHigh
Timedifferent
15-30 min1 h bis mehrere Wochen1-4 Wochen1-6 Wochen
Participantsdifferent
2-61-81-64-10
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeExperiment results, Decision log, Learning summary8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
Continuous improvementLeanExperiments
ExperimentsGrowthAnalyticsValidation
QualityProblem solvingRoot cause
Add more methods