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 Interview |  Product Discovery Opportunity Solution Tree |  Product Strategy Counter Metrics |
|---|---|---|---|---|
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 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 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 a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 30-60 min je Interview | 1-2 h Setup, laufend | 30-60 min |
Participantsdifferent | 2-8 | 5-12 Interviews | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Interview Notes, Opportunity Themes, Customer Quotes | Opportunity Solution Tree, Experiment Backlog, Learning Log | Counter Metric List, Guardrail Definitions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | DiscoveryInterviewsOpportunityCustomer | DiscoveryOutcomesExperimentsOpportunity | MetricsMeasurementStrategyExperiments |