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 |  Domain Modeling Context Map |  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. | 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 | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 1-3 h | 1-5 Tage |
Participantsdifferent | 1-4 | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | 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 | ValidationDemandMVP | Domain-Driven DesignBoundariesStrategy | ValidationExperimentsDemandDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
