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 Change Analysis.
Operations
Change Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree 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 deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.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.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
LowMediumMediumHigh
Timedifferent
20-40 min initial, dann laufend45-120 min2-4 h2-6 h
Participantsdifferent
3-152-62-63-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
ROAM Board, Owner ListChange Matrix, Cause Hypotheses, Validation Questions, Action ListBarrier Inventory, Failure Analysis per Barrier, Action BacklogFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
RiskAgileTrackingAlignment
ChangeRoot causeTroubleshootingComparison
Root causeSafetyIncident
RiskRoot causeSafety
Add more methods