View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Product Discovery Opportunity Solution Tree |  Product Discovery Opportunity Interview |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-2 h Setup, laufend | 30-60 min je Interview |
Participantsdifferent | 2-8 | 2-6 | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Opportunity Solution Tree, Experiment Backlog, Learning Log | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | DiscoveryOutcomesExperimentsOpportunity | DiscoveryInterviewsOpportunityCustomer |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
