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 User Interviews |  UX Design Service Blueprinting |  Knowledge Modeling Event Modeling |  Product Discovery Opportunity Interview |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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. | 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 opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 30–60 min per interview | 0.5-2 Tage | 2-6 h | 30-60 min je Interview |
Participantsdifferent | 1 participant per interview | 6-12 | 2-8 | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Service Blueprint, Fail Points, Ownership Map | Event Model, UI Flow, Commands, Read Models | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | QualitativeResearchCustomerDiscovery | Service designOperationsJourneyBlueprint | EventsBlueprintDomain-Driven DesignBehavior | DiscoveryInterviewsOpportunityCustomer |