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 Problem Interview |  Delivery RAID Log |  Product Discovery Assumption Mapping |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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 | Medium | Low | Medium | Medium |
Timedifferent | 30-60 min je Interview | 30 min Setup, dann laufend | 45-60 min | 1-5 Tage |
Participantsdifferent | 5-12 Interviews | 1-3 maintaining, briefing for everyone | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | RAID Log, Status Report Source | Assumption map, Test backlog, Risk ranking | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | DiscoveryInterviewsValidation | RiskTrackingStakeholdersGovernance | AssumptionsRiskExperimentsValidation | ValidationExperimentsDemandDiscovery |