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 Pre-Mortem |  Architecture Request for Comments |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | 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. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 20–45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min |
Participantsdifferent | 1-3 | Small cross-functional group | 3-20 Reviewer | 2-8 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Risk list, Mitigation plan, Assumption log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskDecisionFailurePlanning | ArchitectureDecisionAsyncGovernance | AssumptionsRiskDecisionDiscovery |