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 MappingCustomer Journey MappingTeam Topologies Interaction ModesSpotify Model Mapping
| Criterion |  Facilitation Expectation Mapping |  UX Research Customer Journey Mapping |  Team Design Team Topologies Interaction Modes |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
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 user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 45-90 min | 2-4 h | Half day | 90-180 min |
Participantsdifferent | 3-12 | 4-10 | Team-Leads plus Architecture | 5-15 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Journey Map, Pain-point List, Opportunity Backlog | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List |
Tagsno overlap | AlignmentStakeholdersTeam | JourneyServiceService design | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis |