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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
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 illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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 keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowHighMediumMedium
Timedifferent
20-60 min2-6 h1-3 h1-4 h
Participantsdifferent
1-43-102-83-8
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathFMEA Table, Risk Priority, Mitigation ActionsCause Tree, Evidence Notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
OperationsReliabilityDocumentation
RiskQualityOperationsRoot cause
Root causeTreeIncidentQuality
Root causeProblem solvingQualityIncident
Add more methods