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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
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.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.
Complexitydifferent
MediumMediumLow
Timedifferent
1-4 WochenAs needed20-60 min
Participantsdifferent
5-204-151-4
Formatdifferent
AsyncWorkshop + asyncAsync
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineIncident Log, Action Tracker, Stakeholder UpdatesRunbook, Checklist, Escalation Path
Tagsno overlap
UX researchTrackingBehavior
IncidentOperationsReliability
OperationsReliabilityDocumentation
Add more methods

Often compared together

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

Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Learning Review.
Operations
Learning Review