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 |  UX Research HEART Framework |  Product Discovery Kano Model |  Product Strategy KPI Tree |
|---|---|---|---|---|
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. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-60 min je Interview | 120 min initial, dann laufend | 1-2 Tage | 90-180 min initial, dann laufend |
Participantsdifferent | 5-12 Interviews | 3-6 | 10-50 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | HEART-GSM Table, Dashboard | Kano Matrix, Feature Classes, Priority Themes | KPI Tree, Owner List |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | MetricsUX researchMeasurementSatisfaction | SatisfactionPrioritizationCustomer | MetricsStrategyAlignmentMeasurement |