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 Red Teaming |  Architecture Architecture Decision Record |  Architecture Risk Storming |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | High | Low | Low | Medium |
Timedifferent | 1-4 h | 15-45 min | 60-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 3-8 | 1-3 | 4-12 | 3-20 Reviewer |
Formatdifferent | Workshop | Async | Workshop | Async |
Outputdifferent | Challenge Findings, Risk Register, Mitigation Plan | ADR File, Decision Log, Rationale | Annotated Diagram, Prioritized Risk List, Action Backlog | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | RiskDecisionSensemaking | ArchitectureRationaleDocumentationGovernance | RiskArchitectureWorkshopValidation | ArchitectureDecisionAsyncGovernance |