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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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 early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.
Complexitydifferent
MediumLow
Timedifferent
30-90 min20–45 min
Participantsdifferent
3-12Small cross-functional group
Formatdifferent
Workshop + asyncWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineRisk list, Mitigation plan, Assumption log
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
RiskDecisionFailurePlanning
Add more methods

Often compared together

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

Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command