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 Architecture Decision Record |  Architecture Risk Storming |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | Multiple workshops over several weeks | 15-45 min | 60-90 min | 45-60 min |
Participantsdifferent | 2-8 | 1-3 | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | ADR File, Decision Log, Rationale | Annotated Diagram, Prioritized Risk List, Action Backlog | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | GrowthBehaviorRetention | ArchitectureRationaleDocumentationGovernance | RiskArchitectureWorkshopValidation | AssumptionsRiskExperimentsValidation |