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 Views and Beyond | ![]() Architecture Architecture Decision Record | ![]() Growth Flywheel |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | Multiple workshops over several weeks | 1-3 Tage | 15-45 min | 60-120 min |
Participantsdifferent | 2-8 | 1-4 | 1-3 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog |
Tagsno overlap | GrowthBehaviorRetention | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance | GrowthRetentionConversion |



