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 Diary Study | ![]() Product Discovery Kano Model | ![]() Operations A3 Problem Solving | ![]() UX Research HEART Framework |
|---|---|---|---|---|
Purposedifferent | 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 features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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-4 Wochen | 1-2 Tage | 45-90 min | 120 min initial, dann laufend |
Participantsdifferent | 5-20 | 10-50 | 2-5 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Kano Matrix, Feature Classes, Priority Themes | A3 Report, Action Plan, Root Cause Analysis | HEART-GSM Table, Dashboard |
Tagsno overlap | UX researchTrackingBehavior | SatisfactionPrioritizationCustomer | LeanProblem solvingCoachingOperations | MetricsUX researchMeasurementSatisfaction |



