View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Causal Loop Diagram |  Architecture Architecture Communication Canvas |  Systems Thinking System Dynamics Simulation |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | System Dynamics Simulation makes assumptions about time, delay, and feedback testable through experiments. It draws relationships, patterns, and feedback loops. The result is captured as a simulation model and scenario reports. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-3 h | 60-120 min | Mehrere Tage bis Wochen | 1-2 Tage |
Participantsdifferent | 2-8 | 2-8 | 1-5 Modellierende, Stakeholder asynchron | 1-4 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Causal Loop Diagram, Feedback Notes, Leverage Points | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Simulation Model, Scenario Reports | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | FeedbackSystems thinkingCausalityDynamics | ArchitectureCommunicationStakeholdersCanvas | Systems thinkingDynamicsSimulationAnalysis | ArchitectureDocumentationCommunication |