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 Architecture Decision Record |  Decision Making Decision Rights Mapping |  Architecture Request for Comments |
|---|---|---|---|---|
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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-4 h | 15-45 min | 90-180 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 3-12 | 1-3 | 4-12 | 3-20 Reviewer |
Formatdifferent | Workshop | Async | Workshop | Async |
Outputdifferent | Team Charter, Working Norms, Role Notes | ADR File, Decision Log, Rationale | Decision Rights Matrix, Agreement | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | TeamAlignmentCollaboration | ArchitectureRationaleDocumentationGovernance | DecisionGovernanceAlignmentResponsibility | ArchitectureDecisionAsyncGovernance |