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 |  Decision Making Force Field Analysis |  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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | Low | Medium |
Timedifferent | Stunden bis wenige Tage | 45-90 min | 1-5 Tage |
Participantsdifferent | 1-4 | 3-12 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Force Field Map, Change Levers, Risk Notes | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | ChangeDecisionStrategy | ValidationExperimentsDemandDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
