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 |  Facilitation Team Charter |  Architecture arc42 |  Team Design Team API |
|---|---|---|---|---|
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 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 2-4 h | 1-2 Tage | Half day initial, dann laufend |
Participantsdifferent | 3-20 Reviewer | 3-12 | 1-4 | Ein Team plus Stakeholder |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Team Charter, Working Norms, Role Notes | Architecture Document, Context View, Runtime View, Deployment View | Team API Document |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | TeamAlignmentCollaboration | ArchitectureDocumentationCommunication | TeamAlignmentCommunicationService |