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 | ![]() Systems Thinking Causal Loop Diagram | ![]() Systems Thinking Stock and Flow Diagram |
|---|---|---|---|---|
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. | 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. | A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 1-4 h | 15-45 min | 1-3 h | 2-6 h |
Participantsdifferent | 1-5 | 1-3 | 2-8 | 1-6 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | Causal Loop Diagram, Feedback Notes, Leverage Points | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses |
Tagsno overlap | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | FeedbackSystems thinkingCausalityDynamics | DynamicsSimulationFeedbackSystems thinking |



