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 System Dynamics Simulation |  Systems Thinking Causal Loop Diagram |  Architecture Risk Storming |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | 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. | 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 | High | Medium | Low | Medium |
Timedifferent | Mehrere Tage bis Wochen | 1-3 h | 60-90 min | 45-60 min |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 2-8 | 4-12 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | Simulation Model, Scenario Reports | Causal Loop Diagram, Feedback Notes, Leverage Points | Annotated Diagram, Prioritized Risk List, Action Backlog | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | FeedbackSystems thinkingCausalityDynamics | RiskArchitectureWorkshopValidation | AssumptionsRiskExperimentsValidation |