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 |  Systems Thinking System Dynamics Simulation |  Architecture Risk Storming |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 h | Mehrere Tage bis Wochen | 60-90 min | 45-60 min |
Participantsdifferent | 2-8 | 1-5 Modellierende, Stakeholder asynchron | 4-12 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Causal Loop Diagram, Feedback Notes, Leverage Points | Simulation Model, Scenario Reports | Annotated Diagram, Prioritized Risk List, Action Backlog | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | FeedbackSystems thinkingCausalityDynamics | Systems thinkingDynamicsSimulationAnalysis | RiskArchitectureWorkshopValidation | AssumptionsRiskExperimentsValidation |