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
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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
LowLowHighMedium
Timedifferent
30-60 min30 min Setup, dann laufend2-6 h2-4 h
Participantsdifferent
2-81-3 maintaining, briefing for everyone3-82-6
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Fishbone Diagram, Cause Categories, Investigation BacklogRAID Log, Status Report SourceFault Tree, Critical Paths, Cause Hypotheses, Control ActionsBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
Root causeQualityOperations
RiskTrackingStakeholdersGovernance
RiskRoot causeSafety
Root causeSafetyIncident
Add more methods