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 |  Systems Thinking Evaporating Cloud |  Product Discovery Solution Interview |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-60 min je Interview | 60-120 min | 30-60 min je Interview | 45-60 min |
Participantsdifferent | 5-12 Interviews | 2-8 | 5-10 Interviews | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Solution Feedback, Objection List, Validation Notes | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | DiscoveryInterviewsValidation | Theory of ConstraintsAssumptionsSystems thinking | ValidationInterviewsPrototype | AssumptionsRiskExperimentsValidation |