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 |  Product Discovery Opportunity Interview |  Domain Modeling Context Map |  Product Discovery Opportunity Solution Tree |
|---|---|---|---|---|
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 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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 30–60 min per interview | 30-60 min je Interview | 1-3 h | 1-2 h Setup, laufend |
Participantsdifferent | 1 participant per interview | 5-12 Interviews | 2-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Interview Notes, Opportunity Themes, Customer Quotes | Context Map, Integration Patterns, Boundary Notes | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | QualitativeResearchCustomerDiscovery | DiscoveryInterviewsOpportunityCustomer | Domain-Driven DesignBoundariesStrategy | DiscoveryOutcomesExperimentsOpportunity |