View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Growth Hooked Model |  Growth Funnel Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Growth Flywheel |
|---|---|---|---|---|
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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | Multiple workshops over several weeks | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 60-120 min |
Participantsdifferent | 2-8 | 1-5 | Evaluation team, architects, and relevant stakeholders | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Funnel report, Drop-off analysis, Optimization hypotheses | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog |
Tagsno overlap | GrowthBehaviorRetention | AnalyticsConversionGrowth | ArchitectureQualityRiskTradeoffsStakeholders | GrowthRetentionConversion |