View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Team Design Team Topologies Interaction Modes |  UX Design Customer Journey Canvas |
|---|---|---|---|
Purposedifferent | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | Half day initial, dann laufend | Half day | 1-3 h |
Participantsdifferent | Ein Team plus Stakeholder | Team-Leads plus Architecture | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Team API Document | Interaction Heat Map, Agreements per Pair | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | TeamAlignmentCommunicationService | TeamAlignmentCollaborationOrganization | JourneyCustomerService designCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
