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 |  Product Discovery Problem Interview |  Domain Modeling Domain Context Map |
|---|---|---|---|
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 the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 30-60 min je Interview | 30-60 min je Interview | 1-3 h |
Participantsdifferent | 5-12 Interviews | 5-12 Interviews | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Problem Evidence, Risk Notes, Customer Segments | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | DiscoveryInterviewsValidation | Domain-Driven DesignContextBoundaries |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
