View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Spotify Model Mapping |  Delivery RAID Log |  Agile ROAM Board |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 90-180 min | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 60-90 min |
Participantsdifferent | 5-15 | 1-3 maintaining, briefing for everyone | 3-15 | 3-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Spotify Model Map, Action List | RAID Log, Status Report Source | ROAM Board, Owner List | Salience Diagram, Strategy per Class |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | StakeholdersFacilitationAlignmentGovernance |