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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Weekly Review.
Operations
Weekly Review
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
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.In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.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
MediumLowMedium
Timedifferent
30-90 min30-60 min1-3 h
Participantsdifferent
3-1213-10
Formatdifferent
Workshop + asyncAsyncWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineUpdated Task System, Weekly Focus, Next ActionsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
ProductivityExecutionPlanning
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

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

Paper illustration for ALPEN Method
Operations
ALPEN Method
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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