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 |  UX Research HEART Framework |  Engineering Goal Question Metric |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 2-4 h | 120 min initial, dann laufend | 90-180 min |
Participantsdifferent | 10-50 | 4-10 | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Journey Map, Pain-point List, Opportunity Backlog | HEART-GSM Table, Dashboard | GQM Table, Metric Profiles |
Tagsno overlap | SatisfactionPrioritizationCustomer | JourneyServiceService design | MetricsUX researchMeasurementSatisfaction | MetricsMeasurementEngineeringAlignment |