View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Design Service Blueprinting | ![]() Innovation Brainstorming | ![]() Knowledge Modeling Event Modeling |
|---|---|---|---|
Purposedifferent | 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 team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | 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. |
Complexitydifferent | High | Low | Medium |
Timedifferent | 0.5-2 Tage | 30-60 min | 2-6 h |
Participantsdifferent | 6-12 | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Idea pool, Theme clusters, Shortlist | Event Model, UI Flow, Commands, Read Models |
Tagsno overlap | Service designOperationsJourneyBlueprint | BrainstormingIdeationCreativityWorkshopDivergence | EventsBlueprintDomain-Driven DesignBehavior |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






