View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Fault Tree Analysis |  Agile ROAM Board |  Delivery RAID Log |
|---|---|---|---|
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. | 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. |
Complexitydifferent | High | Low | Low |
Timedifferent | 2-6 h | 20-40 min initial, dann laufend | 30 min Setup, dann laufend |
Participantsdifferent | 3-8 | 3-15 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | ROAM Board, Owner List | RAID Log, Status Report Source |
Tags1 shared | RiskRoot causeSafety | RiskAgileTrackingAlignment | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
