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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
30-90 min30-90 min45-90 minAs needed
Participantsdifferent
3-121-62-84-15
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Postmortem Doc, Action Items, TimelineDecision Tree, Option Map, Assumption ListAssumption List, Critical Assumptions, Learning PlanIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
DecisionTreeOptions
AssumptionsRiskDecisionDiscovery
IncidentOperationsReliability
Add more methods