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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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.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.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.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
MediumHighMediumMedium
Timedifferent
1-4 WochenHalber Tag1-3 h1-3 h
Participantsdifferent
5-205-203-103-10
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineSimulation Notes, Gaps List, Updated RunbooksProcess Map, Handoff List, Improvement BacklogLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
UX researchTrackingBehavior
ResilienceOperationsIncident
ProcessOperationsImprovement
LearningRetrospectiveIncidentOperations
Add more methods