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)Hypothesis Prioritization CanvasLASR (Lightweight Approach for Software Reviews)Experiment Canvas
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Hypothesis Prioritization Canvas |  Architecture LASR (Lightweight Approach for Software Reviews) |  Product Discovery Experiment Canvas |
|---|---|---|---|---|
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. | 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. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-60 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-8 | 1 or a small team; particularly suitable for 3–4 people | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + 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 | Prioritization Canvas, Hypothesis Backlog | Lean 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 | Completed Experiment Canvas, Success Metric |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ExperimentsPrioritizationDiscoveryHypothesis | ArchitectureQualityRiskAssessmentLean | ExperimentsValidationDiscoveryHypothesis |