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 |  Systems Thinking Leverage Points |  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. | 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. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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 | High | High | Medium |
Timedifferent | 2-6 h | 1-5 Tage | Half day | 2-8 h |
Participantsdifferent | 2-8 | 4-12 | 3-12 | 5-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Leverage Map, Action Strategy | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | ChangeSystems thinkingCapability | Systems thinkingChangeStrategy | Domain-Driven DesignEventsDiscoveryWorkshop |