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 |  Knowledge Modeling Event Modeling |  Innovation Design Charrette |  Innovation Lotus Blossom |
|---|---|---|---|---|
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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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 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 | 2-8 h | 2-6 h | Halber Tag bis mehrere Tage | 45-90 min |
Participantsdifferent | 5-12 | 2-8 | 10-50 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Event Model, UI Flow, Commands, Read Models | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | Domain-Driven DesignEventsDiscoveryWorkshop | EventsBlueprintDomain-Driven DesignBehavior | BrainstormingWorkshopCollaborationIdeation | BrainstormingIdeationCreativityDivergenceWorkshop |