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 | ![]() Knowledge Modeling Shape-First Modeling | ![]() 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. | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | 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 |
Timedifferent | Stunden bis wenige Tage | Halber Tag pro Domain Slice | 1-5 Tage |
Participantsdifferent | 1-4 | 1-4 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Click Data, Interest Signal, Learning Decision |
Tags1 shared | ValidationDemandMVP | Knowledge graphValidationSemantic | ValidationExperimentsDemandDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






