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 |  Systems Thinking Behavior Over Time Graph |  Architecture C4 Model |  Systems Thinking Causal Loop Diagram |
|---|---|---|---|---|
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. | A Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots. | 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. | A Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 20-45 min | 1-4 h | 1-3 h |
Participantsdifferent | 1-3 | 1-10 | 1-5 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Behavior Over Time Graph, Trend Hypotheses, Key Events | Context Diagram, Container Diagram, Component Diagram | Causal Loop Diagram, Feedback Notes, Leverage Points |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Systems thinkingPatternsDynamics | ArchitectureCommunicationVisualization | FeedbackSystems thinkingCausalityDynamics |