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 Kano Model |  UX Research User Interviews |  UX Research HEART Framework |  Engineering Goal Question Metric |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. | 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 | Medium | Low | Medium | Medium |
Timedifferent | 1-2 Tage | 30–60 min per interview | 120 min initial, dann laufend | 90-180 min |
Participantsdifferent | 10-50 | 1 participant per interview | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Interview Notes, Themes, Insight Summary | HEART-GSM Table, Dashboard | GQM Table, Metric Profiles |
Tagsno overlap | SatisfactionPrioritizationCustomer | QualitativeResearchCustomerDiscovery | MetricsUX researchMeasurementSatisfaction | MetricsMeasurementEngineeringAlignment |