View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Opportunity Interview |  UX Research User Interviews |  Knowledge Modeling Event Modeling |  Domain Modeling EventStorming |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 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 | Medium | Low | Medium | Medium |
Timedifferent | 30-60 min je Interview | 30–60 min per interview | 2-6 h | 2-8 h |
Participantsdifferent | 5-12 Interviews | 1 participant per interview | 2-8 | 5-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Interview Notes, Themes, Insight Summary | Event Model, UI Flow, Commands, Read Models | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | QualitativeResearchCustomerDiscovery | EventsBlueprintDomain-Driven DesignBehavior | Domain-Driven DesignEventsDiscoveryWorkshop |