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 Landing Page Test |  Product Discovery Pretotyping |  Architecture Risk Storming |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | When a value proposition first needs to be checked for resonance, it condenses the idea onto a focused entry page. It shows whether language and offering carry interest. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-5 Tage | Stunden bis wenige Tage | 60-90 min | 1-5 Tage |
Participantsdifferent | Nutzertraffic | 1-4 | 4-12 | Nutzertraffic |
Formatdifferent | Async | Workshop + async | Workshop | Async |
Outputdifferent | Landing Page, Conversion Data, Learning Summary | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Annotated Diagram, Prioritized Risk List, Action Backlog | Click Data, Interest Signal, Learning Decision |
Tags1 shared | ValidationConversionMarketing | ValidationDemandMVP | RiskArchitectureWorkshopValidation | ValidationExperimentsDemandDiscovery |