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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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 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
20-40 min initial, dann laufend2-6 h30 min Setup, dann laufend2-4 h
Participantsdifferent
3-153-81-3 maintaining, briefing for everyone2-6
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
ROAM Board, Owner ListFault Tree, Critical Paths, Cause Hypotheses, Control ActionsRAID Log, Status Report SourceBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
RiskAgileTrackingAlignment
RiskRoot causeSafety
RiskTrackingStakeholdersGovernance
Root causeSafetyIncident
Add more methods