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 |  Decision Making Force Field Analysis |  Domain Modeling Context Map |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2-8 h | 45-90 min | 1-3 h | 45-90 min |
Participantsdifferent | 5-12 | 3-12 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Force Field Map, Change Levers, Risk Notes | Context Map, Integration Patterns, Boundary Notes | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | Domain-Driven DesignEventsDiscoveryWorkshop | ChangeDecisionStrategy | Domain-Driven DesignBoundariesStrategy | AssumptionsRiskDecisionDiscovery |