View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Growth Hooked Model |  Growth Flywheel |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | Multiple workshops over several weeks | 60-120 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 2-8 | 3-8 | 3-20 Reviewer |
Formatdifferent | Async | Workshop + async | Workshop | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Hooked loop, Trigger map, Reward design, Ethics check | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | GrowthBehaviorRetention | GrowthRetentionConversion | ArchitectureDecisionAsyncGovernance |