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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Purposedifferent
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.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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
LowMediumLow
Timedifferent
20–45 min30-90 min30-90 min
Participantsdifferent
Small cross-functional group3-122-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logPostmortem Doc, Action Items, TimelineConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
RiskDecisionFailurePlanning
Site Reliability EngineeringIncidentLearningReliability
ConstraintsDecisionPlanningOptions
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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command