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 ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Red Teaming |
|---|---|---|---|
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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. |
Complexitydifferent | Low | High | High |
Timedifferent | 60-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 h |
Participantsdifferent | 4-12 | Evaluation team, architects, and relevant stakeholders | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Challenge Findings, Risk Register, Mitigation Plan |
Tags1 shared | RiskArchitectureWorkshopValidation | ArchitectureQualityRiskTradeoffsStakeholders | RiskDecisionSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
