View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling EventStorming |  Systems Thinking Leverage Points |  Decision Making Force Field Analysis |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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-8 h | Half day | 45-90 min | 1-3 h |
Participantsdifferent | 5-12 | 3-12 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Leverage Map, Action Strategy | Force Field Map, Change Levers, Risk Notes | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | Domain-Driven DesignEventsDiscoveryWorkshop | Systems thinkingChangeStrategy | ChangeDecisionStrategy | Domain-Driven DesignBoundariesStrategy |