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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
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.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 an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.
Complexitydifferent
MediumHighMedium
Timedifferent
1-4 WochenHalber Tag30-90 min
Participantsdifferent
5-205-203-12
Formatdifferent
AsyncWorkshopWorkshop + async
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineSimulation Notes, Gaps List, Updated RunbooksPostmortem Doc, Action Items, Timeline
Tagsno overlap
UX researchTrackingBehavior
ResilienceOperationsIncident
Site Reliability EngineeringIncidentLearningReliability
Add more methods

Often compared together

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

Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis