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 Intervention Mapping |  Decision Making Force Field Analysis |  Domain Modeling Context Map |
|---|---|---|---|---|
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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | 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 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 | Medium | High | Low | Medium |
Timedifferent | 2-6 h | 1-5 Tage | 45-90 min | 1-3 h |
Participantsdifferent | 2-8 | 4-12 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Force Field Map, Change Levers, Risk Notes | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | ChangeSystems thinkingCapability | ChangeDecisionStrategy | Domain-Driven DesignBoundariesStrategy |