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 for Fake Door Test
Product Discovery
Fake Door Test
Paper illustration of a Learning Card with four fields for hypothesis, observation, insight, and action.
Product Discovery
Learning Card
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 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.The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible.
Complexitydifferent
HighMediumMediumLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope2–4 h review as a planning range; preparation and evaluation additional1-5 Tage25-40 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholdersDesigners, developers as users, and facilitationNutzertraffic1-5
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
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 revisionsClick Data, Interest Signal, Learning DecisionLearning Card with evidence and next action
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureEngineeringFeedbackValidationTasks
ValidationExperimentsDemandDiscovery
ExperimentsValidationDiscoveryLearning
Add more methods