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 Diary Study |  Product Strategy Impact Mapping |  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 experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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 | 1-4 Wochen | 45-90 min | 120 min initial, dann laufend |
Participantsdifferent | 10-50 | 5-20 | 3-8 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Diary Entries, Longitudinal Patterns, Experience Timeline | Impact Map, Outcome Hypotheses, Delivery Options | HEART-GSM Table, Dashboard |
Tagsno overlap | SatisfactionPrioritizationCustomer | UX researchTrackingBehavior | OutcomesStrategyBehaviorPlanning | MetricsUX researchMeasurementSatisfaction |