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 |  Delivery RAID Log |  Product Discovery Assumption Mapping |  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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 | Medium |
Timedifferent | Stunden bis wenige Tage | 30 min Setup, dann laufend | 45-60 min | 1-5 Tage |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | RAID Log, Status Report Source | Assumption map, Test backlog, Risk ranking | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | RiskTrackingStakeholdersGovernance | AssumptionsRiskExperimentsValidation | ValidationExperimentsDemandDiscovery |