View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Learning Review |  Team Design Spotify Model Mapping |  Team Design Team Topologies Interaction Modes |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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 teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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 | 1-3 h | 90-180 min | Half day | 45–75 min |
Participantsdifferent | 3-10 | 5-15 | Team-Leads plus Architecture | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Learning Review Notes, System Factors, Improvement Actions | Spotify Model Map, Action List | Interaction Heat Map, Agreements per Pair | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LearningRetrospectiveIncidentOperations | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaborationOrganization | RetrospectiveLearningReflectionTeam |