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