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 ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Assumption 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. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | High | High | Medium |
Timedifferent | 1-4 h | Several meetings plus preparation and analysis; total effort depends on scope | 45-60 min |
Participantsdifferent | 3-8 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Challenge Findings, Risk Register, Mitigation Plan | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Assumption map, Test backlog, Risk ranking |
Tags1 shared | RiskDecisionSensemaking | ArchitectureQualityRiskTradeoffsStakeholders | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
