View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Business Strategy GAP Analysis |  Systems Thinking Wardley Mapping |  Systems Thinking System Dynamics Simulation |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | Wardley Mapping makes visible where an offering stands today and where it can evolve. The method connects user need, value chain, and evolution stages into a strategic basis for platform, build, or buy decisions. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 1-3 h | 1-3 h | Mehrere Tage bis Wochen |
Participantsdifferent | 2-8 | 2-8 | 2-10 | 1-5 Modellierende, Stakeholder asynchron |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Gap Matrix, Action Plan, Risk Notes | Wardley Map, Strategic Options, Evolution Notes | Simulation Model, Scenario Reports |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | StrategyAnalysisPlanning | StrategySystems thinkingDynamics | Systems thinkingDynamicsSimulationAnalysis |