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 |  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. | 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 |
Timedifferent | 30–60 min per interview | 1-2 Tage | 90-180 min |
Participantsdifferent | 1 participant per interview | 10-50 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Themes, Insight Summary | Kano Matrix, Feature Classes, Priority Themes | GQM Table, Metric Profiles |
Tagsno overlap | QualitativeResearchCustomerDiscovery | SatisfactionPrioritizationCustomer | MetricsMeasurementEngineeringAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
