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 |  Architecture Risk Storming |  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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 60-90 min | 20-40 min initial, dann laufend |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-12 | 4-12 | 3-15 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Expectation Map, Alignment Notes, Agreements | Annotated Diagram, Prioritized Risk List, Action Backlog | ROAM Board, Owner List |
Tagsno overlap | RiskTrackingStakeholdersGovernance | AlignmentStakeholdersTeam | RiskArchitectureWorkshopValidation | RiskAgileTrackingAlignment |