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 |  Decision Making Red Teaming |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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. | 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. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h | 15-45 min | 1-2 Tage |
Participantsdifferent | 3-20 Reviewer | 3-8 | 1-3 | 1-4 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Challenge Findings, Risk Register, Mitigation Plan | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskDecisionSensemaking | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |