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 | ![]() Delivery MoSCoW | ![]() Decision Making Decision Tree | ![]() Decision Making Constraint 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. | 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. | For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | Multiple workshops over several weeks | 30-90 min | 30-90 min | 30-90 min |
Participantsdifferent | 2-8 | 3-12 | 1-6 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Prioritized Backlog, Release Scope, Tradeoff Notes | Decision Tree, Option Map, Assumption List | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | GrowthBehaviorRetention | PrioritizationScopeDecision | DecisionTreeOptions | ConstraintsDecisionPlanningOptions |



