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 | ![]() Systems Thinking Future Reality Tree | ![]() Decision Making OODA Loop | ![]() 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. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | 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. | 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 | High | Medium | Low |
Timedifferent | 2-6 h | 2-4 h | 15-60 min je Zyklus | 45-90 min |
Participantsdifferent | 2-8 | 3-8 | 1-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Situation Assessment, Decision Loop, Action Updates | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | Theory of ConstraintsSystems thinkingChange | DecisionChangeLearningStrategy | ChangeDecisionStrategy |



