View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations PDCA Cycle |  Product Discovery Fake Door Test |  Product Discovery Pretotyping |
|---|---|---|---|
Purposedifferent | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 1 h bis mehrere Wochen | 1-5 Tage | Stunden bis wenige Tage |
Participantsdifferent | 1-8 | Nutzertraffic | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Click Data, Interest Signal, Learning Decision | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision |
Tagsno overlap | Continuous improvementLeanExperiments | ValidationExperimentsDemandDiscovery | ValidationDemandMVP |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
