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 API |  Team Design Spotify Model Mapping |  Agile 4Ls Retrospective |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | Half day initial, dann laufend | 90-180 min | 45–75 min | 45-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 5-15 | Team members involved | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Spotify Model Map, Action List | 4Ls Board, Learning Themes, Improvement Actions | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | TeamAlignmentCommunicationService | TeamOrganizationAlignmentDiagnosis | RetrospectiveLearningReflectionTeam | AlignmentStakeholdersTeam |