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 CharterSoftware Architecture CanvasCustomer Journey CanvasArchitecture Communication Canvas
| Criterion |  Facilitation Team Charter |  Architecture Software Architecture Canvas |  UX Design Customer Journey Canvas |  Architecture Architecture Communication 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-4 h | 1-2 h | 1-3 h | 60-120 min |
Participantsdifferent | 3-12 | 3-10 | 3-10 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Team Charter, Working Norms, Role Notes | Architecture Canvas, Goals, Constraints, Quality Attributes | Customer Journey Canvas, Pain Points, Experience Opportunities | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | TeamAlignmentCollaboration | CanvasArchitectureAlignmentWorkshop | JourneyCustomerService designCanvas | ArchitectureCommunicationStakeholdersCanvas |