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 Problem Framing Workshop |  Delivery RAID Log |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
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 team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20-40 min initial, dann laufend | 60-120 min | 30 min Setup, dann laufend | 60–90 min |
Participantsdifferent | 3-15 | 4-10 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | ROAM Board, Owner List | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | RAID Log, Status Report Source | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | RiskAgileTrackingAlignment | FacilitationAlignmentDiscovery | RiskTrackingStakeholdersGovernance | StakeholdersAlignmentFacilitationChange |