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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 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.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.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
MediumMediumLowMedium
Timedifferent
1-4 Wochen30-90 min30-60 min1-3 h
Participantsdifferent
5-203-123-123-10
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelinePostmortem Doc, Action Items, TimelineStart Stop Continue Board, Improvement ActionsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
UX researchTrackingBehavior
Site Reliability EngineeringIncidentLearningReliability
RetrospectiveImprovementTeamReflection
LearningRetrospectiveIncidentOperations
Add more methods