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 ModesStakeholder MappingExpectation MappingSpotify Model Mapping
| Criterion |  Team Design Team Topologies Interaction Modes |  Facilitation Stakeholder Mapping |  Facilitation Expectation Mapping |  Team Design Spotify Model 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | Half day | 60–90 min | 45-90 min | 90-180 min |
Participantsdifferent | Team-Leads plus Architecture | 2-8 | 3-12 | 5-15 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Stakeholder Map, Engagement Plan, Risk Notes | Expectation Map, Alignment Notes, Agreements | Spotify Model Map, Action List |
Tags1 shared | TeamAlignmentCollaborationOrganization | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersTeam | TeamOrganizationAlignmentDiagnosis |