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 Research Customer Journey Mapping |  Facilitation Team Charter |  Architecture Software Architecture Canvas |  UX Design Customer Journey Canvas |
|---|---|---|---|---|
Purposedifferent | 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 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 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 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 | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | 2-4 h | 1-2 h | 1-3 h |
Participantsdifferent | 4-10 | 3-12 | 3-10 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Team Charter, Working Norms, Role Notes | Architecture Canvas, Goals, Constraints, Quality Attributes | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | JourneyServiceService design | TeamAlignmentCollaboration | CanvasArchitectureAlignmentWorkshop | JourneyCustomerService designCanvas |