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 illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
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.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 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
LowHighLowMedium
Timedifferent
30 min Setup, dann laufend2-6 h30-60 min2-4 h
Participantsdifferent
1-3 maintaining, briefing for everyone3-82-82-6
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceFault Tree, Critical Paths, Cause Hypotheses, Control ActionsFishbone Diagram, Cause Categories, Investigation BacklogBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskRoot causeSafety
Root causeQualityOperations
Root causeSafetyIncident
Add more methods