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 Risk Storming |  Architecture Quality Attribute Workshop |  Decision Making Red Teaming |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 60-90 min | 2-4 h | 1-4 h | 45-90 min |
Participantsdifferent | 4-12 | 5-15 | 3-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Quality Scenarios, Priority List, Architecture Concerns | Challenge Findings, Risk Register, Mitigation Plan | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskArchitectureWorkshopValidation | RequirementsArchitectureWorkshop | RiskDecisionSensemaking | AssumptionsRiskDecisionDiscovery |