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 Value Stream Mapping |  Facilitation Stakeholder Mapping |  Delivery RAID Log |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 60–90 min | 30 min Setup, dann laufend | 20-40 min initial, dann laufend |
Participantsdifferent | 4-10 | 2-8 | 1-3 maintaining, briefing for everyone | 3-15 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Stakeholder Map, Engagement Plan, Risk Notes | RAID Log, Status Report Source | ROAM Board, Owner List |
Tagsno overlap | LeanFlowWasteDelivery | StakeholdersAlignmentFacilitationChange | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment |