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 Assumption Surfacing |  Decision Making Red Teaming |  Architecture Request for Comments |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 15-45 min | 45-90 min | 1-4 h | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 2-8 | 3-8 | 3-20 Reviewer |
Formatdifferent | Async | Workshop + async | Workshop | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Assumption List, Critical Assumptions, Learning Plan | Challenge Findings, Risk Register, Mitigation Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskDecisionDiscovery | RiskDecisionSensemaking | ArchitectureDecisionAsyncGovernance |