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 |  Product Discovery Smoke Test |  Product Strategy Counter Metrics |
|---|---|---|---|
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. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. |
Complexitysame | Low | Low | Low |
Timedifferent | Stunden bis wenige Tage | 1-5 Tage | 30-60 min |
Participantsdifferent | 1-4 | Nutzertraffic | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Interest Metrics, Conversion Signal, Learning Note | Counter Metric List, Guardrail Definitions |
Tagsno overlap | ValidationDemandMVP | ValidationExperimentsDemandGrowth | MetricsMeasurementStrategyExperiments |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
