View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Event Modeling |  Decision Making Force Field Analysis |  Decision Making OODA Loop |  Domain Modeling EventStorming |
|---|---|---|---|---|
Purposedifferent | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-6 h | 45-90 min | 15-60 min je Zyklus | 2-8 h |
Participantsdifferent | 2-8 | 3-12 | 1-8 | 5-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Force Field Map, Change Levers, Risk Notes | Situation Assessment, Decision Loop, Action Updates | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | ChangeDecisionStrategy | DecisionChangeLearningStrategy | Domain-Driven DesignEventsDiscoveryWorkshop |