View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Usability Testing | ![]() Innovation Lean Startup | ![]() Product Discovery Fake Door Test | ![]() Product Discovery Pretotyping |
|---|---|---|---|---|
Purposedifferent | When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 1-2 h je Session | Wochen bis Monate je Lernzyklus | 1-5 Tage | Stunden bis wenige Tage |
Participantsdifferent | Based on research question | 2-8 | Nutzertraffic | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Usability Issues, Severity List, Recommendations | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Click Data, Interest Signal, Learning Decision | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision |
Tags1 shared | ValidationUXPrototype | LeanStartupValidationMVP | ValidationExperimentsDemandDiscovery | ValidationDemandMVP |



