View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Team Topologies Interaction Modes4Ls RetrospectiveSailboat RetrospectiveSpotify Model Mapping
| Criterion |  Team Design Team Topologies Interaction Modes |  Agile 4Ls Retrospective |  Agile Sailboat Retrospective |  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. | 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 a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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 | 45–75 min | 45-90 min | 90-180 min |
Participantsdifferent | Team-Leads plus Architecture | Team members involved | 4-12 | 5-15 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | 4Ls Board, Learning Themes, Improvement Actions | Sailboat Board, Risks, Improvement Actions | Spotify Model Map, Action List |
Tags1 shared | TeamAlignmentCollaborationOrganization | RetrospectiveLearningReflectionTeam | RetrospectiveTeamImprovement | TeamOrganizationAlignmentDiagnosis |