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 |  Architecture Request for Comments |  Decision Making Pre-Mortem |
|---|---|---|---|
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. | 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. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 20–45 min |
Participantsdifferent | 1-3 | 3-20 Reviewer | Small cross-functional group |
Formatdifferent | Async | Async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance | RiskDecisionFailurePlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
