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 Pretotyping |  Delivery Monte Carlo Forecasting |  Product Discovery Fake Door Test |
|---|---|---|---|
Purposedifferent | 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 scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | 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 | Low | High | Medium |
Timedifferent | Stunden bis wenige Tage | 30-90 min Setup, danach laufend | 1-5 Tage |
Participantsdifferent | 1-4 | 1-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Forecast Percentiles, Throughput Dataset, Risk Communication | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | ForecastingFlowDelivery | ValidationExperimentsDemandDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
