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 Solution Interview |  Product Discovery Outcome-Driven Innovation |  Systems Thinking Evaporating Cloud |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 30-60 min je Interview | Mehrere Wochen | 60-120 min | 45-60 min |
Participantsdifferent | 5-10 Interviews | 2-6 researchers plus sample | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ValidationInterviewsPrototype | OutcomesInnovationResearchQuantitative | Theory of ConstraintsAssumptionsSystems thinking | AssumptionsRiskExperimentsValidation |