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 Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier 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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
LowHighHighMedium
Timedifferent
20-60 min2-6 h2-6 h2-4 h
Participantsdifferent
1-43-103-82-6
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathFMEA Table, Risk Priority, Mitigation ActionsFault Tree, Critical Paths, Cause Hypotheses, Control ActionsBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
OperationsReliabilityDocumentation
RiskQualityOperationsRoot cause
RiskRoot causeSafety
Root causeSafetyIncident
Add more methods