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 |  UX Research Customer Journey Mapping |  Architecture Software Architecture Canvas |  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. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | Medium | Low | Low |
Timedifferent | 2-4 h | 2-4 h | 1-2 h | Half day initial, dann laufend |
Participantsdifferent | 3-12 | 4-10 | 3-10 | Ein Team plus Stakeholder |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Team Charter, Working Norms, Role Notes | Journey Map, Pain-point List, Opportunity Backlog | Architecture Canvas, Goals, Constraints, Quality Attributes | Team API Document |
Tagsno overlap | TeamAlignmentCollaboration | JourneyServiceService design | CanvasArchitectureAlignmentWorkshop | TeamAlignmentCommunicationService |