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 Process Mapping |  Operations Learning Review |  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. | 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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 | Medium | Low |
Timedifferent | 90-180 min | 1-3 h | 1-3 h | 45–75 min |
Participantsdifferent | 5-15 | 3-10 | 3-10 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Process Map, Handoff List, Improvement Backlog | Learning Review Notes, System Factors, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | ProcessOperationsImprovement | LearningRetrospectiveIncidentOperations | RetrospectiveLearningReflectionTeam |