View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Force Field Analysis |  Team Design Spotify Model Mapping |  Agile Start Stop Continue |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 90-180 min | 30-60 min | 45–75 min |
Participantsdifferent | 3-12 | 5-15 | 3-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Spotify Model Map, Action List | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ChangeDecisionStrategy | TeamOrganizationAlignmentDiagnosis | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |