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)Experiment CanvasFake Door Test
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Experiment Canvas |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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 experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. | 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 | 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 | 1-5 Tage |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | Designers, developers as users, and facilitation | 1-5 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | 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 | Completed Experiment Canvas, Success Metric | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureEngineeringFeedbackValidationTasks | ExperimentsValidationDiscoveryHypothesis | ValidationExperimentsDemandDiscovery |