View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Lean Startup |  Product Discovery Pretotyping |  Domain Modeling Context Map |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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. | 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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | Medium | Low | Medium | Medium |
Timedifferent | Wochen bis Monate je Lernzyklus | Stunden bis wenige Tage | 1-3 h | 1-5 Tage |
Participantsdifferent | 2-8 | 1-4 | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Context Map, Integration Patterns, Boundary Notes | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | LeanStartupValidationMVP | ValidationDemandMVP | Domain-Driven DesignBoundariesStrategy | ValidationExperimentsDemandDiscovery |