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 Research Affinity Diagramming |  Knowledge Modeling Event Modeling |  UX Design Service Blueprinting |  Domain Modeling EventStorming |
|---|---|---|---|---|
Purposedifferent | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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 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 | High | Medium |
Timedifferent | 45–90 min | 2-6 h | 0.5-2 Tage | 2-8 h |
Participantsdifferent | 3-10 | 2-8 | 6-12 | 5-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Event Model, UI Flow, Commands, Read Models | Service Blueprint, Fail Points, Ownership Map | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | SynthesisQualitativeRoot cause | EventsBlueprintDomain-Driven DesignBehavior | Service designOperationsJourneyBlueprint | Domain-Driven DesignEventsDiscoveryWorkshop |