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 Opportunity Interview |  Delivery RAID Log |  Product Discovery Problem Interview |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | 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 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-60 min je Interview | 30 min Setup, dann laufend | 30-60 min je Interview | 45-60 min |
Participantsdifferent | 5-12 Interviews | 1-3 maintaining, briefing for everyone | 5-12 Interviews | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | RAID Log, Status Report Source | Problem Evidence, Risk Notes, Customer Segments | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | RiskTrackingStakeholdersGovernance | DiscoveryInterviewsValidation | AssumptionsRiskExperimentsValidation |