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 Flywheel | ![]() Architecture C4 Model |
|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 15-45 min | 60-120 min | 1-4 h |
Participantsdifferent | 1-3 | 3-8 | 1-5 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | GrowthRetentionConversion | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






