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 Change Analysis |  Delivery RAID Log |  Operations Fault Tree Analysis |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 45-120 min | 30 min Setup, dann laufend | 2-6 h | 20-40 min initial, dann laufend |
Participantsdifferent | 2-6 | 1-3 maintaining, briefing for everyone | 3-8 | 3-15 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | RAID Log, Status Report Source | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | ROAM Board, Owner List |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | RiskTrackingStakeholdersGovernance | RiskRoot causeSafety | RiskAgileTrackingAlignment |