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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
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.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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 many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses.
Complexitysame
MediumMediumMediumMedium
Timedifferent
60-120 minAs neededMultiple workshops over several weeks1-3 h
Participantsdifferent
3-84-152-81-5
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Flywheel Map, Friction Points, Growth Levers, Experiment BacklogIncident Log, Action Tracker, Stakeholder UpdatesHooked loop, Trigger map, Reward design, Ethics checkFunnel report, Drop-off analysis, Optimization hypotheses
Tagsno overlap
GrowthRetentionConversion
IncidentOperationsReliability
GrowthBehaviorRetention
AnalyticsConversionGrowth
Add more methods