View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Team CharterCustomer Journey CanvasSoftware Architecture CanvasArchitecture Inception Canvas
| Criterion |  Facilitation Team Charter |  UX Design Customer Journey Canvas |  Architecture Software Architecture Canvas |  Architecture Architecture Inception Canvas |
|---|---|---|---|---|
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 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 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. | 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 | Medium | Medium | Low | Low |
Timedifferent | 2-4 h | 1-3 h | 1-2 h | 1-2 h |
Participantsdifferent | 3-12 | 3-10 | 3-10 | 3-8 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Customer Journey Canvas, Pain Points, Experience Opportunities | Architecture Canvas, Goals, Constraints, Quality Attributes | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | TeamAlignmentCollaboration | JourneyCustomerService designCanvas | CanvasArchitectureAlignmentWorkshop | AlignmentArchitectureCanvas |