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 of Hooked Model with its method-specific working model.
Growth
Hooked Model
Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
Paper illustration for Flywheel.
Growth
Flywheel
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design.In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage.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.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
Multiple workshops over several weeks1-3 h60-120 min1-4 Wochen
Participantsdifferent
2-83-83-81-6
Formatdifferent
Workshop + asyncWorkshopWorkshopAsync
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkFailure Scenarios, Risk Notes, Control Gaps, Test and Response ActionsFlywheel Map, Friction Points, Growth Levers, Experiment BacklogExperiment results, Decision log, Learning summary
Tagsno overlap
GrowthBehaviorRetention
FailureResilienceRisk
GrowthRetentionConversion
ExperimentsGrowthAnalyticsValidation
Add more methods