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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects 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 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.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.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.
Complexitydifferent
LowMediumMediumHigh
Timedifferent
20-60 min30-90 min1-3 h2-6 h
Participantsdifferent
1-41-62-83-10
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathDecision Tree, Option Map, Assumption ListCause Tree, Evidence Notes, CountermeasuresFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
OperationsReliabilityDocumentation
DecisionTreeOptions
Root causeTreeIncidentQuality
RiskQualityOperationsRoot cause
Add more methods