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 Request for Comments | ![]() Decision Making Decision Rights Mapping | ![]() Architecture Architecture Inception Canvas |
|---|---|---|---|---|
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 RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | Multiple workshops over several weeks | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 1-2 h |
Participantsdifferent | 2-8 | 3-20 Reviewer | 4-12 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | GrowthBehaviorRetention | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility | AlignmentArchitectureCanvas |



