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 | ![]() Facilitation Decision Jam |
|---|---|---|---|---|
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 a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 2-8 h | 15-60 min je Zyklus | 60-90 min |
Participantsdifferent | 3-12 | 5-12 | 1-8 | 4-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Situation Assessment, Decision Loop, Action Updates | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | ChangeDecisionStrategy | Domain-Driven DesignEventsDiscoveryWorkshop | DecisionChangeLearningStrategy | FacilitationDecisionProblem solvingWorkshop |



