View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile 4Ls Retrospective |  Team Design Spotify Model Mapping |  Facilitation Alignment Mapping |  Business Strategy McKinsey 7S |
|---|---|---|---|---|
Purposedifferent | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 45–75 min | 90-180 min | 1-2 h | 2-4 h |
Participantsdifferent | Team members involved | 5-15 | 4-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Spotify Model Map, Action List | Alignment Map, Open Issues, Decision Questions | 7S Assessment, Alignment Gaps, Change Actions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersStrategyFacilitation | OrganizationStrategyAlignmentChange |