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 |  Facilitation Expectation Mapping |  Delivery RAID Log |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 90-180 min | 45-90 min | 30 min Setup, dann laufend | 1-2 h |
Participantsdifferent | 5-15 | 3-12 | 1-3 maintaining, briefing for everyone | 4-12 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements | RAID Log, Status Report Source | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam | RiskTrackingStakeholdersGovernance | AlignmentStakeholdersStrategyFacilitation |