View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Delivery RAID Log |  Facilitation Consensus Workshop |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | 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. | 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 a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | 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 | Low | Medium | Low |
Timedifferent | 60-90 min | 30 min Setup, dann laufend | 1-3 h | 20-40 min initial, dann laufend |
Participantsdifferent | 4-12 | 1-3 maintaining, briefing for everyone | 5-30 | 3-15 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | RAID Log, Status Report Source | Consensus Clusters, Theme Titles, Priority Areas | ROAM Board, Owner List |
Tagsno overlap | RiskArchitectureWorkshopValidation | RiskTrackingStakeholdersGovernance | FacilitationConsensusWorkshopAlignment | RiskAgileTrackingAlignment |