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 |  Agile WSJF |  Engineering Kanban |  Operations 5 Whys |
|---|---|---|---|---|
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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-4 Wochen | 45-90 min | Ongoing | 15-30 min |
Participantsdifferent | 5-20 | 3-10 | 2-12 | 2-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Ranked Backlog, Cost-of-Delay Assumptions | Kanban board, WIP policies, Flow metrics | Root cause notes, Countermeasures |
Tagsno overlap | UX researchTrackingBehavior | LeanEconomicsSequencePrioritization | FlowVisual managementDelivery | Root causeIncidentLeanProblem solving |