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 |  Domain Modeling Context Map |  Innovation Brainstorming |  Innovation Design Charrette |
|---|---|---|---|---|
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. | 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 team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-8 h | 1-3 h | 30-60 min | Halber Tag bis mehrere Tage |
Participantsdifferent | 5-12 | 2-8 | 4-12 | 10-50 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Context Map, Integration Patterns, Boundary Notes | Idea pool, Theme clusters, Shortlist | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction |
Tagsno overlap | Domain-Driven DesignEventsDiscoveryWorkshop | Domain-Driven DesignBoundariesStrategy | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingWorkshopCollaborationIdeation |