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
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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.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.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.
Complexitysame
MediumMediumMedium
Timedifferent
Multiple workshops over several weeks1-3 hAs needed
Participantsdifferent
2-81-54-15
Formatdifferent
Workshop + asyncAsyncWorkshop + async
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkFunnel report, Drop-off analysis, Optimization hypothesesIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
GrowthBehaviorRetention
AnalyticsConversionGrowth
IncidentOperationsReliability
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.