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 |  Team Design Team Topologies Interaction Modes |  Facilitation Expectation 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. | 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 teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 90-180 min | 30 min Setup, dann laufend | Half day | 45-90 min |
Participantsdifferent | 5-15 | 1-3 maintaining, briefing for everyone | Team-Leads plus Architecture | 3-12 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | RAID Log, Status Report Source | Interaction Heat Map, Agreements per Pair | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | RiskTrackingStakeholdersGovernance | TeamAlignmentCollaborationOrganization | AlignmentStakeholdersTeam |