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 |
|---|---|---|---|
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. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 2-6 h | 1-5 Tage | 45-90 min |
Participantsdifferent | 2-8 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | ChangeSystems thinkingCapability | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






