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 |  Product Strategy KPI Tree |  Engineering Goal Question Metric |
|---|---|---|---|---|
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 metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-60 min je Interview | 30-60 min je Interview | 90-180 min initial, dann laufend | 90-180 min |
Participantsdifferent | 5-12 Interviews | 5-12 Interviews | 3-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Problem Evidence, Risk Notes, Customer Segments | KPI Tree, Owner List | GQM Table, Metric Profiles |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | DiscoveryInterviewsValidation | MetricsStrategyAlignmentMeasurement | MetricsMeasurementEngineeringAlignment |