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 Request for Comments | ![]() Decision Making Constraint Analysis | ![]() Decision Making Argument Mapping |
|---|---|---|---|---|
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 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. | 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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | 1-4 h | 1-3 Wochen vom Draft bis zur Entscheidung | 30-90 min | 1-3 h |
Participantsdifferent | 3-8 | 3-20 Reviewer | 2-8 | 1-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Challenge Findings, Risk Register, Mitigation Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Argument Map, Evidence Gaps, Decision Rationale |
Tags1 shared | RiskDecisionSensemaking | ArchitectureDecisionAsyncGovernance | ConstraintsDecisionPlanningOptions | SensemakingDecisionRationale |



