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 API |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
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 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 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 90-180 min | Half day initial, dann laufend | 45-90 min | 45-90 min |
Participantsdifferent | 5-15 | Ein Team plus Stakeholder | 4-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Team API Document | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tags1 shared | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCommunicationService | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |