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 | ![]() UX Design Service Blueprinting | ![]() 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. | 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-8 h | 0.5-2 Tage | 45-90 min |
Participantsdifferent | 5-12 | 6-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Service Blueprint, Fail Points, Ownership Map | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | Domain-Driven DesignEventsDiscoveryWorkshop | Service designOperationsJourneyBlueprint | BrainstormingIdeationCreativityDivergenceWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






