View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Design Customer Journey Canvas | ![]() Team Design Team Topologies Interaction Modes | ![]() Team Design Spotify Model Mapping |
|---|---|---|---|
Purposedifferent | When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | Half day | 90-180 min |
Participantsdifferent | 3-10 | Team-Leads plus Architecture | 5-15 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List |
Tagsno overlap | JourneyCustomerService designCanvas | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






