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 Design Service Blueprinting | ![]() 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 service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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 | High | Low |
Timedifferent | 2-6 h | 0.5-2 Tage | 45-90 min |
Participantsdifferent | 2-8 | 6-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Service Blueprint, Fail Points, Ownership Map | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | Service designOperationsJourneyBlueprint | BrainstormingIdeationCreativityDivergenceWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






