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 |  Domain Modeling Context Map |  Domain Modeling Domain Context Map |  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 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 a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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 | Medium | Medium | Medium |
Timedifferent | 30–60 min per interview | 1-3 h | 1-3 h | 30-60 min je Interview |
Participantsdifferent | 1 participant per interview | 2-8 | 3-10 | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | QualitativeResearchCustomerDiscovery | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries | DiscoveryInterviewsOpportunityCustomer |