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 |  Domain Modeling EventStorming |  Product Discovery Opportunity Solution Tree |
|---|---|---|---|---|
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. | 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 discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-60 min je Interview | 30–60 min per interview | 2-8 h | 1-2 h Setup, laufend |
Participantsdifferent | 5-12 Interviews | 1 participant per interview | 5-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Interview Notes, Themes, Insight Summary | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tags1 shared | DiscoveryInterviewsOpportunityCustomer | QualitativeResearchCustomerDiscovery | Domain-Driven DesignEventsDiscoveryWorkshop | DiscoveryOutcomesExperimentsOpportunity |