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 After-Action Review |  Operations ABC Analysis |  Agile Sprint Retrospective |
|---|---|---|---|---|
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. | 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 many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-4 Wochen | 20-45 min | 30-60 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 5-20 | 3-12 | 1-5 | Scrum Team |
Formatdifferent | Async | Workshop + async | Async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Lessons learned, Action items, Event summary | ABC Classification, Focus Rules, Control List | Improvement actions, Team agreements |
Tagsno overlap | UX researchTrackingBehavior | LearningOperationsImprovement | PrioritizationOperationsPortfolio | RetrospectiveImprovementLearning |