View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Team Charter |  Architecture Architecture Inception Canvas |  Team Design Team API |  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 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. | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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 | Low | Medium |
Timedifferent | 2-4 h | 1-2 h | Half day initial, dann laufend | 60-120 min |
Participantsdifferent | 3-12 | 3-8 | Ein Team plus Stakeholder | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Team Charter, Working Norms, Role Notes | Inception Canvas, Risks, Goal List, Open Questions | Team API Document | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | TeamAlignmentCollaboration | AlignmentArchitectureCanvas | TeamAlignmentCommunicationService | ArchitectureCommunicationStakeholdersCanvas |