View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:System Dynamics SimulationARID (Active Reviews for Intermediate Designs)Causal Loop Diagram
| Criterion |  Systems Thinking System Dynamics Simulation |  Architecture ARID (Active Reviews for Intermediate Designs) |  Systems Thinking Causal Loop Diagram |
|---|---|---|---|
Purposedifferent | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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 | High | Medium | Medium |
Timedifferent | Mehrere Tage bis Wochen | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | Designers, developers as users, and facilitation | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | Simulation Model, Scenario Reports | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Causal Loop Diagram, Feedback Notes, Leverage Points |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | ArchitectureEngineeringFeedbackValidationTasks | FeedbackSystems thinkingCausalityDynamics |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
