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 |  Architecture Request for Comments |  Growth Flywheel |  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. | 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. | 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. | 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 | 1-3 Wochen vom Draft bis zur Entscheidung | 60-120 min | 1-3 h |
Participantsdifferent | 2-8 | 3-20 Reviewer | 3-8 | 1-5 |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Funnel report, Drop-off analysis, Optimization hypotheses |
Tagsno overlap | GrowthBehaviorRetention | ArchitectureDecisionAsyncGovernance | GrowthRetentionConversion | AnalyticsConversionGrowth |