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 for Flywheel.
Growth
Flywheel
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
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.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.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.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 min60-120 minMultiple workshops over several weeks1-4 Wochen
Participantsdifferent
1-43-82-81-6
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
Runbook, Checklist, Escalation PathFlywheel Map, Friction Points, Growth Levers, Experiment BacklogHooked loop, Trigger map, Reward design, Ethics checkExperiment results, Decision log, Learning summary
Tagsno overlap
OperationsReliabilityDocumentation
GrowthRetentionConversion
GrowthBehaviorRetention
ExperimentsGrowthAnalyticsValidation
Add more methods