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 | ![]() Innovation Design Charrette | ![]() Innovation Starbursting | ![]() Domain Modeling EventStorming |
|---|---|---|---|---|
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. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. | Helps clarify ideas, open questions, and testable next steps in concrete terms. It opens the thinking space, collects ideas, and leads to testable options. The result is captured as a star-shaped question map, question list, and assumption list. | 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 | Medium | Low | Medium |
Timedifferent | 1-3 h | Halber Tag bis mehrere Tage | 30-60 min | 2-8 h |
Participantsdifferent | 2-8 | 10-50 | 3-10 | 5-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Star-Shaped Question Map, Question List, Assumption List | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | BrainstormingWorkshopCollaborationIdeation | BrainstormingIdeationWorkshopDiscovery | Domain-Driven DesignEventsDiscoveryWorkshop |



