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 |  Architecture Architecture Inception 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 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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | Half day initial, dann laufend | 2-4 h | 1-3 h | 1-2 h |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Team Charter, Working Norms, Role Notes | Customer Journey Canvas, Pain Points, Experience Opportunities | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | TeamAlignmentCommunicationService | TeamAlignmentCollaboration | JourneyCustomerService designCanvas | AlignmentArchitectureCanvas |