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 Pre-Mortem |  Decision Making Red Teaming |  Decision Making Constraint Analysis |
|---|---|---|---|---|
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. | 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. | 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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 20–45 min | 1-4 h | 30-90 min |
Participantsdifferent | 3-20 Reviewer | Small cross-functional group | 3-8 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Risk list, Mitigation plan, Assumption log | Challenge Findings, Risk Register, Mitigation Plan | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tags1 shared | ArchitectureDecisionAsyncGovernance | RiskDecisionFailurePlanning | RiskDecisionSensemaking | ConstraintsDecisionPlanningOptions |