View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Facilitation Team Charter |  Architecture Architecture Inception Canvas |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | Half day initial, dann laufend | 2-4 h | 1-2 h | 1-2 h |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 3-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Team Charter, Working Norms, Role Notes | Inception Canvas, Risks, Goal List, Open Questions | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tags1 shared | TeamAlignmentCommunicationService | TeamAlignmentCollaboration | AlignmentArchitectureCanvas | CanvasArchitectureAlignmentWorkshop |