View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile ROAM Board | ![]() Facilitation Consensus Workshop | ![]() Delivery RAID Log |
|---|---|---|---|
Purposedifferent | 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 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 20-40 min initial, dann laufend | 1-3 h | 30 min Setup, dann laufend |
Participantsdifferent | 3-15 | 5-30 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | ROAM Board, Owner List | Consensus Clusters, Theme Titles, Priority Areas | RAID Log, Status Report Source |
Tagsno overlap | RiskAgileTrackingAlignment | FacilitationConsensusWorkshopAlignment | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






