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 Domain Context Map |  Innovation Design Charrette |  Domain Modeling EventStorming |  Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. | 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 central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | Halber Tag bis mehrere Tage | 2-8 h | 45-90 min |
Participantsdifferent | 3-10 | 10-50 | 5-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | Domain-Driven DesignContextBoundaries | BrainstormingWorkshopCollaborationIdeation | Domain-Driven DesignEventsDiscoveryWorkshop | BrainstormingIdeationCreativityDivergenceWorkshop |