View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Product Strategy Lean Canvas | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Product Discovery Experiment Canvas |
|---|---|---|---|
Purposedifferent | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | 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 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 | Medium | High | Low |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 1-6 | Evaluation team, architects, and relevant stakeholders | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Lean Canvas, Core Assumptions, Experiment Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Completed Experiment Canvas, Success Metric |
Tagsno overlap | StartupLeanAssumptionsBusiness model | ArchitectureQualityRiskTradeoffsStakeholders | ExperimentsValidationDiscoveryHypothesis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






