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 Team Topologies Interaction Modes |  Delivery RAID Log |  Agile ROAM Board |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | Half day | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 90-180 min |
Participantsdifferent | Team-Leads plus Architecture | 1-3 maintaining, briefing for everyone | 3-15 | 5-15 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | RAID Log, Status Report Source | ROAM Board, Owner List | Spotify Model Map, Action List |
Tagsno overlap | TeamAlignmentCollaborationOrganization | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | TeamOrganizationAlignmentDiagnosis |