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 |  Facilitation Team Charter |  Agile 4Ls Retrospective |  Facilitation Expectation Mapping |
|---|---|---|---|---|
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 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. | 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 | Medium | Medium | Low | Low |
Timedifferent | 90-180 min | 2-4 h | 45–75 min | 45-90 min |
Participantsdifferent | 5-15 | 3-12 | Team members involved | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Team Charter, Working Norms, Role Notes | 4Ls Board, Learning Themes, Improvement Actions | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaboration | RetrospectiveLearningReflectionTeam | AlignmentStakeholdersTeam |