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 | ![]() Decision Making Assumption Surfacing | ![]() Agile ROAM Board | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 20-40 min initial, dann laufend | 1-2 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | 3-15 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Assumption List, Critical Assumptions, Learning Plan | ROAM Board, Owner List | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | AssumptionsRiskDecisionDiscovery | RiskAgileTrackingAlignment | AlignmentStakeholdersStrategyFacilitation |



