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 | ![]() Engineering Failure Scenario Analysis | ![]() Growth North Star Metric | ![]() Growth Pirate Metrics AARRR |
|---|---|---|---|---|
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. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | When product teams track many metrics, the view of the actual customer outcome easily gets lost. A North Star Metric bundles growth, usage, and value contribution into one signal that makes the system's direction visible. | For products with complex usage paths, overall growth alone is too coarse to reveal bottlenecks. Pirate Metrics breaks the relationship with the product into consecutive stages and shows where the funnel actually leaks. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | Multiple workshops over several weeks | 1-3 h | 1-2 h | 1-2 h Setup, laufend |
Participantsdifferent | 2-8 | 3-8 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | North Star metric, Input metric tree, Measurement cadence | AARRR funnel, Metric baseline, Experiment backlog |
Tagsno overlap | GrowthBehaviorRetention | FailureResilienceRisk | GrowthMetricsAlignmentRetention | GrowthMetricsExperiments |



