View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Product Discovery Pretotyping |  Product Discovery Fake Door Test |  Product Discovery Riskiest Assumption Test |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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 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. | When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | Stunden bis wenige Tage | 1-5 Tage | 1-2 Wochen pro Iteration |
Participantsdifferent | 3-12 | 1-4 | Nutzertraffic | 2-6 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Click Data, Interest Signal, Learning Decision | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | AlignmentStakeholdersTeam | ValidationDemandMVP | ValidationExperimentsDemandDiscovery | ExperimentsValidationDiscoveryAssumptions |