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
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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
Purposedifferent
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 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.
Complexitydifferent
LowLowHighHigh
Timedifferent
30-60 min20-60 min2-6 h2-6 h
Participantsdifferent
2-81-43-103-8
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Fishbone Diagram, Cause Categories, Investigation BacklogRunbook, Checklist, Escalation PathFMEA Table, Risk Priority, Mitigation ActionsFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
Root causeQualityOperations
OperationsReliabilityDocumentation
RiskQualityOperationsRoot cause
RiskRoot causeSafety
Add more methods