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 Context Map |  Domain Modeling EventStorming |  Facilitation Problem Framing Workshop |
|---|---|---|---|
Purposedifferent | 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. | 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. | When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | 2-8 h | 60-120 min |
Participantsdifferent | 2-8 | 5-12 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignEventsDiscoveryWorkshop | FacilitationAlignmentDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
