View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)ATAM (Architecture Tradeoff Analysis Method)Riskiest Assumption TestFake Door Test
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Riskiest Assumption Test |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 Wochen pro Iteration | 1-5 Tage |
Participantsdifferent | Designers, developers as users, and facilitation | Evaluation team, architects, and relevant stakeholders | 2-6 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Prioritized Assumption List, Test Plan, Results Report | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureQualityRiskTradeoffsStakeholders | ExperimentsValidationDiscoveryAssumptions | ValidationExperimentsDemandDiscovery |