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 |  Facilitation Team Charter |  UX Design Customer Journey Canvas |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
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 a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | Half day initial, dann laufend | 2-4 h | 1-3 h | Half day |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 3-10 | Team-Leads plus Architecture |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Team Charter, Working Norms, Role Notes | Customer Journey Canvas, Pain Points, Experience Opportunities | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | TeamAlignmentCommunicationService | TeamAlignmentCollaboration | JourneyCustomerService designCanvas | TeamAlignmentCollaborationOrganization |