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 |  Decision Making Force Field Analysis |  Agile 4Ls Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 90-180 min | 45-90 min | 45–75 min | 30-60 min |
Participantsdifferent | 5-15 | 3-12 | Team members involved | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Force Field Map, Change Levers, Risk Notes | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | ChangeDecisionStrategy | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection |