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 for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.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
HighLowHighMedium
Timedifferent
2-6 h20-40 min initial, dann laufendMehrere Tage bis Wochen2-4 h
Participantsdifferent
3-83-152-62-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsROAM Board, Owner ListMORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
RiskRoot causeSafety
RiskAgileTrackingAlignment
Root causeSafetySystemicIncident
Root causeSafetyIncident
Add more methods