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 OODA Loop |  Domain Modeling Context Map |  Decision Making Force Field Analysis |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2-6 h | 15-60 min je Zyklus | 1-3 h | 45-90 min |
Participantsdifferent | 2-8 | 1-8 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Situation Assessment, Decision Loop, Action Updates | Context Map, Integration Patterns, Boundary Notes | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | DecisionChangeLearningStrategy | Domain-Driven DesignBoundariesStrategy | ChangeDecisionStrategy |