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 |  Domain Modeling Context Map |  Domain Modeling Domain Context Map |  Product Discovery Problem Interview |
|---|---|---|---|---|
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 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 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-60 min je Interview | 1-3 h | 1-3 h | 30-60 min je Interview |
Participantsdifferent | 5-12 Interviews | 2-8 | 3-10 | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map | Problem Evidence, Risk Notes, Customer Segments |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries | DiscoveryInterviewsValidation |