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 |  Delivery MoSCoW |  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. | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-4 Wochen | 1-2 Tage | 30-90 min | 120 min initial, dann laufend |
Participantsdifferent | 5-20 | 10-50 | 3-12 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Kano Matrix, Feature Classes, Priority Themes | Prioritized Backlog, Release Scope, Tradeoff Notes | HEART-GSM Table, Dashboard |
Tagsno overlap | UX researchTrackingBehavior | SatisfactionPrioritizationCustomer | PrioritizationScopeDecision | MetricsUX researchMeasurementSatisfaction |