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 Inception Canvas | ![]() Architecture Software Architecture Canvas | ![]() 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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | Low | Low | Medium |
Timedifferent | Multiple workshops over several weeks | 1-2 h | 1-2 h | 60-120 min |
Participantsdifferent | 2-8 | 3-8 | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Inception Canvas, Risks, Goal List, Open Questions | Architecture Canvas, Goals, Constraints, Quality Attributes | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog |
Tagsno overlap | GrowthBehaviorRetention | AlignmentArchitectureCanvas | CanvasArchitectureAlignmentWorkshop | GrowthRetentionConversion |



