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 Request for Comments |  Team Design Team API |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | 1-3 Wochen vom Draft bis zur Entscheidung | Half day initial, dann laufend | Half day |
Participantsdifferent | 3-12 | 3-20 Reviewer | Ein Team plus Stakeholder | Team-Leads plus Architecture |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Team API Document | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | TeamAlignmentCollaboration | ArchitectureDecisionAsyncGovernance | TeamAlignmentCommunicationService | TeamAlignmentCollaborationOrganization |