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 | ![]() Systems Thinking Future Reality Tree | ![]() 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. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | 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 | High | Medium |
Timedifferent | Stunden bis wenige Tage | 2-4 h | 1-5 Tage |
Participantsdifferent | 1-4 | 3-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | Theory of ConstraintsSystems thinkingChange | ValidationExperimentsDemandDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






