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 |  UX Design Service Blueprinting |  Facilitation Team Charter |  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 a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | Half day initial, dann laufend | 0.5-2 Tage | 2-4 h | 1-3 h |
Participantsdifferent | Ein Team plus Stakeholder | 6-12 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Service Blueprint, Fail Points, Ownership Map | Team Charter, Working Norms, Role Notes | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | TeamAlignmentCommunicationService | Service designOperationsJourneyBlueprint | TeamAlignmentCollaboration | JourneyCustomerService designCanvas |