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 | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Product Discovery Learning Card | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-5 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 25-40 min | 45-60 min |
Participantsdifferent | Nutzertraffic | Evaluation team, architects, and relevant stakeholders | 1-5 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Click Data, Interest Signal, Learning Decision | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Learning Card with evidence and next action | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ValidationExperimentsDemandDiscovery | ArchitectureQualityRiskTradeoffsStakeholders | ExperimentsValidationDiscoveryLearning | AssumptionsRiskExperimentsValidation |



