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 After-Action Review |  Operations Process Mapping |
|---|---|---|---|---|
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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-4 Wochen | 1-2 Tage | 20-45 min | 1-3 h |
Participantsdifferent | 5-20 | 10-50 | 3-12 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Kano Matrix, Feature Classes, Priority Themes | Lessons learned, Action items, Event summary | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | UX researchTrackingBehavior | SatisfactionPrioritizationCustomer | LearningOperationsImprovement | ProcessOperationsImprovement |