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 Flywheel |  Architecture Request for Comments |  Growth Funnel Analysis |
|---|---|---|---|---|
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. | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 | Medium | Medium | Medium | Medium |
Timedifferent | Multiple workshops over several weeks | 60-120 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h |
Participantsdifferent | 2-8 | 3-8 | 3-20 Reviewer | 1-5 |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Funnel report, Drop-off analysis, Optimization hypotheses |
Tagsno overlap | GrowthBehaviorRetention | GrowthRetentionConversion | ArchitectureDecisionAsyncGovernance | AnalyticsConversionGrowth |