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 Kepner-Tregoe
Operations
Kepner-Tregoe
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.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.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.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
LowHighHighMedium
Timedifferent
15-30 min2-8 h1-4 Wochen1-4 h
Participantsdifferent
2-62-81-63-8
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresProblem Analysis, Decision Analysis, Risk PlanExperiment results, Decision log, Learning summaryProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
Problem solvingRoot causeDecisionOperations
ExperimentsGrowthAnalyticsValidation
Root causeProblem solvingQualityIncident
Add more methods