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 |  Agile 4Ls Retrospective |  Team Design Team API |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
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 a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 90-180 min | 45–75 min | Half day initial, dann laufend | Half day |
Participantsdifferent | 5-15 | Team members involved | Ein Team plus Stakeholder | Team-Leads plus Architecture |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Spotify Model Map, Action List | 4Ls Board, Learning Themes, Improvement Actions | Team API Document | Interaction Heat Map, Agreements per Pair |
Tags1 shared | TeamOrganizationAlignmentDiagnosis | RetrospectiveLearningReflectionTeam | TeamAlignmentCommunicationService | TeamAlignmentCollaborationOrganization |