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 |  Decision Making Red Teaming |  Decision Making Pre-Mortem |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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. | 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 | Medium | High | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h | 20–45 min | 45-90 min |
Participantsdifferent | 3-20 Reviewer | 3-8 | Small cross-functional group | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Challenge Findings, Risk Register, Mitigation Plan | Risk list, Mitigation plan, Assumption log | Assumption List, Critical Assumptions, Learning Plan |
Tags1 shared | ArchitectureDecisionAsyncGovernance | RiskDecisionSensemaking | RiskDecisionFailurePlanning | AssumptionsRiskDecisionDiscovery |