View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Team Topologies Interaction ModesSpotify Model MappingBlameless PostmortemExpectation Mapping
| Criterion |  Team Design Team Topologies Interaction Modes |  Team Design Spotify Model Mapping |  DevOps Blameless Postmortem |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | Half day | 90-180 min | 30-90 min | 45-90 min |
Participantsdifferent | Team-Leads plus Architecture | 5-15 | 3-12 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List | Postmortem Doc, Action Items, Timeline | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis | Site Reliability EngineeringIncidentLearningReliability | AlignmentStakeholdersTeam |