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
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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 has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
MediumHighHighLow
Timedifferent
60-120 min2-6 h1-4 Wochen30-60 min
Participantsdifferent
3-83-101-62-8
Formatdifferent
WorkshopWorkshopAsyncWorkshop
Outputdifferent
Flywheel Map, Friction Points, Growth Levers, Experiment BacklogFMEA Table, Risk Priority, Mitigation ActionsExperiment results, Decision log, Learning summaryFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
GrowthRetentionConversion
RiskQualityOperationsRoot cause
ExperimentsGrowthAnalyticsValidation
Root causeQualityOperations
Add more methods