View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Operations Fault Tree Analysis |  Facilitation Stakeholder Mapping |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | Low | High | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 2-6 h | 60–90 min | 20-40 min initial, dann laufend |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-8 | 2-8 | 3-15 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Stakeholder Map, Engagement Plan, Risk Notes | ROAM Board, Owner List |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RiskRoot causeSafety | StakeholdersAlignmentFacilitationChange | RiskAgileTrackingAlignment |