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 | ![]() Product Discovery Opportunity Solution Tree | ![]() Domain Modeling Context Map | ![]() Product Strategy Counter Metrics |
|---|---|---|---|---|
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 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 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 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 | Low | Medium | Medium | Low |
Timedifferent | 30–60 min per interview | 1-2 h Setup, laufend | 1-3 h | 30-60 min |
Participantsdifferent | 1 participant per interview | 2-6 | 2-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Opportunity Solution Tree, Experiment Backlog, Learning Log | Context Map, Integration Patterns, Boundary Notes | Counter Metric List, Guardrail Definitions |
Tagsno overlap | QualitativeResearchCustomerDiscovery | DiscoveryOutcomesExperimentsOpportunity | Domain-Driven DesignBoundariesStrategy | MetricsMeasurementStrategyExperiments |



