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 Customer Journey Mapping |  Product Strategy KPI Tree |  UX Research HEART Framework |
|---|---|---|---|---|
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 a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 2-4 h | 90-180 min initial, dann laufend | 120 min initial, dann laufend |
Participantsdifferent | 10-50 | 4-10 | 3-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Journey Map, Pain-point List, Opportunity Backlog | KPI Tree, Owner List | HEART-GSM Table, Dashboard |
Tagsno overlap | SatisfactionPrioritizationCustomer | JourneyServiceService design | MetricsStrategyAlignmentMeasurement | MetricsUX researchMeasurementSatisfaction |