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 Systems Mapping | ![]() Systems Thinking System Dynamics Simulation | ![]() Systems Thinking Evaporating Cloud |
|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 h | Mehrere Tage bis Wochen | 60-120 min |
Participantsdifferent | 3-12 | 1-5 Modellierende, Stakeholder asynchron | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | Simulation Model, Scenario Reports | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tags1 shared | Systems thinkingMappingBoundariesChange | Systems thinkingDynamicsSimulationAnalysis | Theory of ConstraintsAssumptionsSystems thinking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






