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 Kano Model |  Product Strategy KPI Tree |  Engineering Goal Question Metric |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30–60 min per interview | 1-2 Tage | 90-180 min initial, dann laufend | 90-180 min |
Participantsdifferent | 1 participant per interview | 10-50 | 3-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Themes, Insight Summary | Kano Matrix, Feature Classes, Priority Themes | KPI Tree, Owner List | GQM Table, Metric Profiles |
Tagsno overlap | QualitativeResearchCustomerDiscovery | SatisfactionPrioritizationCustomer | MetricsStrategyAlignmentMeasurement | MetricsMeasurementEngineeringAlignment |