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 | ![]() UX Research Customer Journey Mapping | ![]() Innovation Lotus Blossom |
|---|---|---|---|
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 user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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 | Low |
Timedifferent | 2-6 h | 2-4 h | 45-90 min |
Participantsdifferent | 2-8 | 4-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Journey Map, Pain-point List, Opportunity Backlog | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | JourneyServiceService design | BrainstormingIdeationCreativityDivergenceWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






