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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
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.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.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.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
LowMediumMediumMedium
Timedifferent
20-60 min30-90 min1-2 h Setup, laufend1-3 h
Participantsdifferent
1-43-1213-10
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathPostmortem Doc, Action Items, TimelineAction Lists, Project List, Review RoutineLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
OperationsReliabilityDocumentation
Site Reliability EngineeringIncidentLearningReliability
ProductivityPlanningTasksExecution
LearningRetrospectiveIncidentOperations
Add more methods