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 Contextual Inquiry |  UX Research HEART Framework |  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 work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | 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 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-3 Wochen | 120 min initial, dann laufend | 90-180 min initial, dann laufend |
Participantsdifferent | 10-50 | 4-12 Beobachtungen | 3-6 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Field Notes, Workflow Insights, Pain Points | HEART-GSM Table, Dashboard | KPI Tree, Owner List |
Tagsno overlap | SatisfactionPrioritizationCustomer | UX researchObservationContext | MetricsUX researchMeasurementSatisfaction | MetricsStrategyAlignmentMeasurement |