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)
Paper illustration of Hypothesis Prioritization Canvas with a method-specific labelled workspace.
Product Discovery
Hypothesis Prioritization Canvas
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
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.When many hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.
Complexitydifferent
HighMediumMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope60-90 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
Evaluation team, architects, and relevant stakeholders3-81 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPrioritization Canvas, Hypothesis BacklogLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
ExperimentsPrioritizationDiscoveryHypothesis
ArchitectureQualityRiskAssessmentLean
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Paper illustration of a Test Card with four fields for hypothesis, test, metric, and success threshold.
Product Discovery
Test Card
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas