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 Discovery Jobs to Be Done |  Product Strategy Impact Mapping |
|---|---|---|---|---|
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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-4 Wochen | 1-3 Wochen | 45-90 min |
Participantsdifferent | 10-50 | 5-20 | 5-12 Interviews | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Diary Entries, Longitudinal Patterns, Experience Timeline | Job Stories, Outcome Statements, Opportunity List | Impact Map, Outcome Hypotheses, Delivery Options |
Tagsno overlap | SatisfactionPrioritizationCustomer | UX researchTrackingBehavior | CustomerOutcomesNeeds | OutcomesStrategyBehaviorPlanning |