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 Architecture Decision Record |  Decision Making Risk Matrix |  Architecture Views and Beyond |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Low | Low | Medium | Medium |
Timedifferent | 15-45 min | 30-60 min | 1-3 Tage | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 3-10 | 1-4 | 3-20 Reviewer |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Risk Matrix, Top Risk List | Architecture Views, Cross-view Notes, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskDecisionPrioritizationAssessment | DocumentationStakeholdersArchitecture | ArchitectureDecisionAsyncGovernance |