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 |  Facilitation Expectation Mapping |  Agile ROAM Board |  Decision Making Decision Rights 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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 20-40 min initial, dann laufend | 90-180 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-12 | 3-15 | 4-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Expectation Map, Alignment Notes, Agreements | ROAM Board, Owner List | Decision Rights Matrix, Agreement |
Tagsno overlap | RiskTrackingStakeholdersGovernance | AlignmentStakeholdersTeam | RiskAgileTrackingAlignment | DecisionGovernanceAlignmentResponsibility |