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 Smoke Test.
Product Discovery
Smoke Test
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.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.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
LowLowHighMedium
Timedifferent
15-30 min1-5 Tage1-4 Wochen1-4 h
Participantsdifferent
2-6Nutzertraffic1-63-8
Formatdifferent
WorkshopAsyncAsyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summaryProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Root causeProblem solvingQualityIncident
Add more methods