View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Spotify Model MappingTeam Topologies Interaction ModesBlameless Postmortem4Ls Retrospective
| Criterion |  Team Design Spotify Model Mapping |  Team Design Team Topologies Interaction Modes |  DevOps Blameless Postmortem |  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. | 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. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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 | Half day | 30-90 min | 45–75 min |
Participantsdifferent | 5-15 | Team-Leads plus Architecture | 3-12 | Team members involved |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Spotify Model Map, Action List | Interaction Heat Map, Agreements per Pair | Postmortem Doc, Action Items, Timeline | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaborationOrganization | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveLearningReflectionTeam |