View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)ARID (Active Reviews for Intermediate Designs)Risk MatrixAssumption Mapping
| Criterion | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Decision Making Risk Matrix | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min | 45-60 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | Designers, developers as users, and facilitation | 3-10 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Risk Matrix, Top Risk List | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureEngineeringFeedbackValidationTasks | RiskDecisionPrioritizationAssessment | AssumptionsRiskExperimentsValidation |



