View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Event Modeling |  Domain Modeling EventStorming |  Innovation Lotus Blossom |  Innovation Rapid Ideation |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When a decision needs to be prepared quickly, the method generates many solution-close variants in a short time. It deliberately relies on pace to undercut self-censorship and perfectionism. This quickly produces a usable field for prioritization and further work. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2-6 h | 2-8 h | 45-90 min | 5-20 min |
Participantsdifferent | 2-8 | 5-12 | 3-10 | 1-20 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Lotus Diagram, Idea Themes, Shortlist | Ideenpool, Roh-Shortlist, Cluster |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | Domain-Driven DesignEventsDiscoveryWorkshop | BrainstormingIdeationCreativityDivergenceWorkshop | BrainstormingIdeationDivergenceSpeed |