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
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
MediumMediumLow
Timedifferent
1-4 WochenAs needed30-60 min
Participantsdifferent
5-204-153-12
Formatdifferent
AsyncWorkshop + asyncWorkshop
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineIncident Log, Action Tracker, Stakeholder UpdatesStart Stop Continue Board, Improvement Actions
Tagsno overlap
UX researchTrackingBehavior
IncidentOperationsReliability
RetrospectiveImprovementTeamReflection
Add more methods

Often compared together

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

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
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective