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 Process Mapping |  DevOps Game Day |  Operations After-Action Review |
|---|---|---|---|---|
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 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-4 Wochen | 1-3 h | Halber Tag | 20-45 min |
Participantsdifferent | 5-20 | 3-10 | 5-20 | 3-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Process Map, Handoff List, Improvement Backlog | Simulation Notes, Gaps List, Updated Runbooks | Lessons learned, Action items, Event summary |
Tagsno overlap | UX researchTrackingBehavior | ProcessOperationsImprovement | ResilienceOperationsIncident | LearningOperationsImprovement |