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 Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree 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.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.When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent
LowMediumLowMedium
Timedifferent
15-30 min1-4 h1-5 Tage1-3 h
Participantsdifferent
2-63-8Nutzertraffic2-8
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop
Outputdifferent
Root cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanInterest Metrics, Conversion Signal, Learning NoteCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
ValidationExperimentsDemandGrowth
Root causeTreeIncidentQuality
Add more methods