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 |  Facilitation Team Charter |  Team Design Team API |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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 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 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 2-4 h | Half day initial, dann laufend | 60-120 min |
Participantsdifferent | 3-10 | 3-12 | Ein Team plus Stakeholder | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Team Charter, Working Norms, Role Notes | Team API Document | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | JourneyCustomerService designCanvas | TeamAlignmentCollaboration | TeamAlignmentCommunicationService | ArchitectureCommunicationStakeholdersCanvas |