View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Riskiest Assumption TestATAM (Architecture Tradeoff Analysis Method)ARID (Active Reviews for Intermediate Designs)Assumption Surfacing
| Criterion |  Product Discovery Riskiest Assumption Test |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. | 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. | 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 | Medium | High | Medium | Low |
Timedifferent | 1-2 Wochen pro Iteration | Several meetings plus preparation and analysis; total effort depends on scope | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min |
Participantsdifferent | 2-6 | Evaluation team, architects, and relevant stakeholders | Designers, developers as users, and facilitation | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized Assumption List, Test Plan, Results Report | 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 | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | ExperimentsValidationDiscoveryAssumptions | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskDecisionDiscovery |