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 |  Architecture arc42 |  Decision Making Pre-Mortem |
|---|---|---|---|
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. | 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. | 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 | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 Tage | 20–45 min |
Participantsdifferent | 3-20 Reviewer | 1-4 | Small cross-functional group |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Document, Context View, Runtime View, Deployment View | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ArchitectureDocumentationCommunication | RiskDecisionFailurePlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
