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 Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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 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.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
LowMediumHighLow
Timedifferent
20-60 min30-90 min2-6 h30-60 min
Participantsdifferent
1-41-63-102-8
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathDecision Tree, Option Map, Assumption ListFMEA Table, Risk Priority, Mitigation ActionsFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
OperationsReliabilityDocumentation
DecisionTreeOptions
RiskQualityOperationsRoot cause
Root causeQualityOperations
Add more methods