View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Solo Brainstorming | ![]() Knowledge Modeling Event Modeling | ![]() Innovation Lotus Blossom | ![]() Domain Modeling EventStorming |
|---|---|---|---|---|
Purposedifferent | For an individual thinking problem with no counterpart immediately available, the method creates a protected space for one's own approaches. It prevents outside opinions from narrowing thinking too early. This lets ideas mature before they go into a group format. | 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 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 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 | Low | Medium | Low | Medium |
Timedifferent | 15-60 min | 2-6 h | 45-90 min | 2-8 h |
Participantsdifferent | 1 | 2-8 | 3-10 | 5-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | Personal Idea List, Sketches or Mind Map, Pre-Read for Group Session | Event Model, UI Flow, Commands, Read Models | Lotus Diagram, Idea Themes, Shortlist | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | BrainstormingIdeationAsync | EventsBlueprintDomain-Driven DesignBehavior | BrainstormingIdeationCreativityDivergenceWorkshop | Domain-Driven DesignEventsDiscoveryWorkshop |



