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 |  Product Strategy KPI Tree |
|---|---|---|---|
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. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-2 Tage | 30–60 min per interview | 90-180 min initial, dann laufend |
Participantsdifferent | 10-50 | 1 participant per interview | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Interview Notes, Themes, Insight Summary | KPI Tree, Owner List |
Tagsno overlap | SatisfactionPrioritizationCustomer | QualitativeResearchCustomerDiscovery | MetricsStrategyAlignmentMeasurement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
