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 Discovery Fake Door Test | ![]() Product Discovery Hypothesis Prioritization Canvas | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 1-5 Tage | 60-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | Nutzertraffic | 3-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | Click Data, Interest Signal, Learning Decision | Prioritization Canvas, Hypothesis Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | ValidationExperimentsDemandDiscovery | ExperimentsPrioritizationDiscoveryHypothesis | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






