View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Team Charter |  Architecture Architecture Inception Canvas |  UX Research Customer Journey Mapping |  Team Design Team API |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2-4 h | 1-2 h | 2-4 h | Half day initial, dann laufend |
Participantsdifferent | 3-12 | 3-8 | 4-10 | Ein Team plus Stakeholder |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Team Charter, Working Norms, Role Notes | Inception Canvas, Risks, Goal List, Open Questions | Journey Map, Pain-point List, Opportunity Backlog | Team API Document |
Tagsno overlap | TeamAlignmentCollaboration | AlignmentArchitectureCanvas | JourneyServiceService design | TeamAlignmentCommunicationService |