methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
Paper illustration for Fake Door Test
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 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
HighMediumMediumMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope2–4 h review as a planning range; preparation and evaluation additional1-2 Wochen pro Iteration1-5 Tage
Participantsdifferent
Evaluation team, architects, and relevant stakeholdersDesigners, developers as users, and facilitation2-6Nutzertraffic
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsPrioritized Assumption List, Test Plan, Results ReportClick Data, Interest Signal, Learning Decision
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureEngineeringFeedbackValidationTasks
ExperimentsValidationDiscoveryAssumptions
ValidationExperimentsDemandDiscovery
Add more methods