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 Flywheel | ![]() Growth Hooked Model | ![]() Delivery MoSCoW | ![]() Growth North Star Metric |
|---|---|---|---|---|
Purposedifferent | 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. | 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 a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 60-120 min | Multiple workshops over several weeks | 30-90 min | 1-2 h |
Participantsdifferent | 3-8 | 2-8 | 3-12 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Hooked loop, Trigger map, Reward design, Ethics check | Prioritized Backlog, Release Scope, Tradeoff Notes | North Star metric, Input metric tree, Measurement cadence |
Tagsno overlap | GrowthRetentionConversion | GrowthBehaviorRetention | PrioritizationScopeDecision | GrowthMetricsAlignmentRetention |



