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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
Paper illustration for Flywheel.
Growth
Flywheel
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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.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
LowMediumMediumHigh
Timedifferent
20-60 minMultiple workshops over several weeks60-120 min1-4 Wochen
Participantsdifferent
1-42-83-81-6
Formatdifferent
AsyncWorkshop + asyncWorkshopAsync
Outputdifferent
Runbook, Checklist, Escalation PathHooked loop, Trigger map, Reward design, Ethics checkFlywheel Map, Friction Points, Growth Levers, Experiment BacklogExperiment results, Decision log, Learning summary
Tagsno overlap
OperationsReliabilityDocumentation
GrowthBehaviorRetention
GrowthRetentionConversion
ExperimentsGrowthAnalyticsValidation
Add more methods