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 |  Agile ROAM Board |  Decision Making Red Teaming |
|---|---|---|---|
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. | 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 strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. |
Complexitydifferent | Low | Low | High |
Timedifferent | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 1-4 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-15 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | ROAM Board, Owner List | Challenge Findings, Risk Register, Mitigation Plan |
Tags1 shared | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | RiskDecisionSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
