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 MappingArchitecture Inception CanvasArchitecture Communication Canvas
| Criterion | ![]() Facilitation Team Charter | ![]() Team Design Spotify Model Mapping | ![]() Architecture Architecture Inception 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 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. | 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-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Team Charter, Working Norms, Role Notes | Spotify Model Map, Action List | Inception Canvas, Risks, Goal List, Open Questions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | TeamAlignmentCollaboration | TeamOrganizationAlignmentDiagnosis | AlignmentArchitectureCanvas | ArchitectureCommunicationStakeholdersCanvas |



