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 C4 Model | ![]() Architecture Architecture Decision Record | ![]() Growth Hooked Model |
|---|---|---|---|
Purposedifferent | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 1-4 h | 15-45 min | Multiple workshops over several weeks |
Participantsdifferent | 1-5 | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | Hooked loop, Trigger map, Reward design, Ethics check |
Tagsno overlap | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | GrowthBehaviorRetention |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






