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 Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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 a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
MediumHighMediumLow
Timedifferent
30-90 min2-6 h1-3 h30-60 min
Participantsdifferent
3-123-102-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineFMEA Table, Risk Priority, Mitigation ActionsCause Tree, Evidence Notes, CountermeasuresFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
RiskQualityOperationsRoot cause
Root causeTreeIncidentQuality
Root causeQualityOperations
Add more methods