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 Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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 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 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.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 min1-3 h30-60 min2-6 h
Participantsdifferent
1-42-82-83-10
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathCause Tree, Evidence Notes, CountermeasuresFishbone Diagram, Cause Categories, Investigation BacklogFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
OperationsReliabilityDocumentation
Root causeTreeIncidentQuality
Root causeQualityOperations
RiskQualityOperationsRoot cause
Add more methods