View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Team Design Team Topologies Interaction Modes |  Facilitation Team Charter |
|---|---|---|---|
Purposedifferent | 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 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. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | Half day | 2-4 h |
Participantsdifferent | 3-20 Reviewer | Team-Leads plus Architecture | 3-12 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Interaction Heat Map, Agreements per Pair | Team Charter, Working Norms, Role Notes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | TeamAlignmentCollaborationOrganization | TeamAlignmentCollaboration |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
