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 Software Architecture Canvas |  Decision Making RAPID |  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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | 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 | Medium | Medium |
Timedifferent | 1-4 h | 1-2 h | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 3-8 | 3-10 | 3-12 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop | Workshop + async | Async |
Outputdifferent | Challenge Findings, Risk Register, Mitigation Plan | Architecture Canvas, Goals, Constraints, Quality Attributes | RAPID Role Map, Recommendation, Decision Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | RiskDecisionSensemaking | CanvasArchitectureAlignmentWorkshop | DecisionRolesGovernance | ArchitectureDecisionAsyncGovernance |