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 |  Team Design Team Topologies Interaction Modes |  Team Design Team API |  Facilitation Team Charter |
|---|---|---|---|---|
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 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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 90-180 min | Half day | Half day initial, dann laufend | 2-4 h |
Participantsdifferent | 5-15 | Team-Leads plus Architecture | Ein Team plus Stakeholder | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Spotify Model Map, Action List | Interaction Heat Map, Agreements per Pair | Team API Document | Team Charter, Working Norms, Role Notes |
Tags2 shared | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaborationOrganization | TeamAlignmentCommunicationService | TeamAlignmentCollaboration |