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 |  Innovation Lean Startup |  Domain Modeling EventStorming |  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. | 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 a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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 | Medium | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | Wochen bis Monate je Lernzyklus | 2-8 h | 1-5 Tage |
Participantsdifferent | 1-4 | 2-8 | 5-12 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | LeanStartupValidationMVP | Domain-Driven DesignEventsDiscoveryWorkshop | ValidationExperimentsDemandDiscovery |