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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and 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.
Complexitydifferent
LowMediumLowHigh
Timedifferent
20-60 min30-90 min20–45 min2-6 h
Participantsdifferent
1-41-6Small cross-functional group3-10
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathDecision Tree, Option Map, Assumption ListRisk list, Mitigation plan, Assumption logFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
OperationsReliabilityDocumentation
DecisionTreeOptions
RiskDecisionFailurePlanning
RiskQualityOperationsRoot cause
Add more methods