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 | ![]() Business Strategy McKinsey 7S | ![]() Agile 4Ls 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. | McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 90-180 min | 2-4 h | 45–75 min |
Participantsdifferent | 5-15 | 3-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | 7S Assessment, Alignment Gaps, Change Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | OrganizationStrategyAlignmentChange | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






