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 CharterSpotify Model MappingSoftware Architecture CanvasArchitecture Communication Canvas
| Criterion |  Facilitation Team Charter |  Team Design Spotify Model Mapping |  Architecture Software Architecture 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. | When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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 Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | 90-180 min | 1-2 h | 60-120 min |
Participantsdifferent | 3-12 | 5-15 | 3-10 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Team Charter, Working Norms, Role Notes | Spotify Model Map, Action List | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | TeamAlignmentCollaboration | TeamOrganizationAlignmentDiagnosis | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |