methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Diary Study.
UX Research
Diary Study
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Learning Review.
Operations
Learning 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.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
MediumLowMedium
Timedifferent
1-4 Wochen20-45 min1-3 h
Participantsdifferent
5-203-123-10
Formatdifferent
AsyncWorkshop + asyncWorkshop
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineLessons learned, Action items, Event summaryLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
UX researchTrackingBehavior
LearningOperationsImprovement
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem