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 |  Operations After-Action Review |  Operations Process Mapping |  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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 | Low | Medium | Low |
Timedifferent | 90-180 min | 20-45 min | 1-3 h | 45–75 min |
Participantsdifferent | 5-15 | 3-12 | 3-10 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Lessons learned, Action items, Event summary | Process Map, Handoff List, Improvement Backlog | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | LearningOperationsImprovement | ProcessOperationsImprovement | RetrospectiveLearningReflectionTeam |