View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Team Charter | ![]() Agile 4Ls Retrospective | ![]() Team Design Spotify Model Mapping | ![]() Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | 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 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's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2-4 h | 45–75 min | 90-180 min | 30-60 min |
Participantsdifferent | 3-12 | Team members involved | 5-15 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | 4Ls Board, Learning Themes, Improvement Actions | Spotify Model Map, Action List | Emotion Board, Themes, Action Items |
Tags1 shared | TeamAlignmentCollaboration | RetrospectiveLearningReflectionTeam | TeamOrganizationAlignmentDiagnosis | RetrospectiveTeamReflection |



