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 Topologies Interaction ModesArchitecture Decision RecordRequest for CommentsTeam Charter
| Criterion |  Team Design Team Topologies Interaction Modes |  Architecture Architecture Decision Record |  Architecture Request for Comments |  Facilitation Team Charter |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | Half day | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 2-4 h |
Participantsdifferent | Team-Leads plus Architecture | 1-3 | 3-20 Reviewer | 3-12 |
Formatdifferent | Workshop | Async | Async | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Team Charter, Working Norms, Role Notes |
Tagsno overlap | TeamAlignmentCollaborationOrganization | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance | TeamAlignmentCollaboration |