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 ModesWorking AgreementsSpotify Model MappingExpectation Mapping
| Criterion |  Team Design Team Topologies Interaction Modes |  Agile Working Agreements |  Team Design Spotify Model Mapping |  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 collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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 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 | Low | Medium | Low |
Timedifferent | Half day | 45-90 min | 90-180 min | 45-90 min |
Participantsdifferent | Team-Leads plus Architecture | 3-12 | 5-15 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Working Agreements, Team Norms, Review Cadence | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | TeamAlignmentCollaborationOrganization | TeamCollaborationAgile | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam |