View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Pre-Mortem |  Architecture arc42 |  Architecture Request for Comments |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | 20–45 min | 1-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min |
Participantsdifferent | Small cross-functional group | 1-4 | 3-20 Reviewer | 2-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Architecture Document, Context View, Runtime View, Deployment View | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskDecisionFailurePlanning | ArchitectureDocumentationCommunication | ArchitectureDecisionAsyncGovernance | AssumptionsRiskDecisionDiscovery |