View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Force Field Analysis |  Domain Modeling EventStorming |  Decision Making OODA Loop |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 45-90 min | 2-8 h | 15-60 min je Zyklus | 1-3 h |
Participantsdifferent | 3-12 | 5-12 | 1-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Situation Assessment, Decision Loop, Action Updates | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | ChangeDecisionStrategy | Domain-Driven DesignEventsDiscoveryWorkshop | DecisionChangeLearningStrategy | Domain-Driven DesignBoundariesStrategy |