View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Consensus Workshop |  Delivery RAID Log |  Agile ROAM Board |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 60–90 min |
Participantsdifferent | 5-30 | 1-3 maintaining, briefing for everyone | 3-15 | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Consensus Clusters, Theme Titles, Priority Areas | RAID Log, Status Report Source | ROAM Board, Owner List | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | FacilitationConsensusWorkshopAlignment | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | StakeholdersAlignmentFacilitationChange |