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
Paper illustration for Flywheel.
Growth
Flywheel
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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.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.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.
Complexitydifferent
MediumHighMediumLow
Timedifferent
60-120 min1-4 Wochen1-4 h15-30 min
Participantsdifferent
3-81-63-82-6
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Flywheel Map, Friction Points, Growth Levers, Experiment BacklogExperiment results, Decision log, Learning summaryProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanRoot cause notes, Countermeasures
Tagsno overlap
GrowthRetentionConversion
ExperimentsGrowthAnalyticsValidation
Root causeProblem solvingQualityIncident
Root causeIncidentLeanProblem solving
Add more methods