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 Customer Journey Mapping | ![]() Product Discovery Kano Model | ![]() UX Research HEART Framework |
|---|---|---|---|
Purposedifferent | 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 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 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 |
Timedifferent | 2-4 h | 1-2 Tage | 120 min initial, dann laufend |
Participantsdifferent | 4-10 | 10-50 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Kano Matrix, Feature Classes, Priority Themes | HEART-GSM Table, Dashboard |
Tagsno overlap | JourneyServiceService design | SatisfactionPrioritizationCustomer | MetricsUX researchMeasurementSatisfaction |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






