View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Expectation MappingSpotify Model MappingCommunication PlanTeam Topologies Interaction Modes
| Criterion |  Facilitation Expectation Mapping |  Team Design Spotify Model Mapping |  Delivery Communication Plan |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | 90-180 min | 45-90 min | Half day |
Participantsdifferent | 3-12 | 5-15 | 2-6 | Team-Leads plus Architecture |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Spotify Model Map, Action List | Communication Plan, Channel Matrix, Message Cadence | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | AlignmentStakeholdersTeam | TeamOrganizationAlignmentDiagnosis | CommunicationStakeholdersDeliveryPlanning | TeamAlignmentCollaborationOrganization |