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 |  Operations ABC Analysis |  DevOps Game Day |  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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | 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 | Low | High | Low |
Timedifferent | 1-4 Wochen | 30-60 min | Halber Tag | 15-30 min |
Participantsdifferent | 5-20 | 1-5 | 5-20 | 2-6 |
Formatdifferent | Async | Async | Workshop | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | ABC Classification, Focus Rules, Control List | Simulation Notes, Gaps List, Updated Runbooks | Root cause notes, Countermeasures |
Tagsno overlap | UX researchTrackingBehavior | PrioritizationOperationsPortfolio | ResilienceOperationsIncident | Root causeIncidentLeanProblem solving |