View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Evaporating Cloud |  Product Discovery Outcome-Driven Innovation |  Product Discovery Smoke Test |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 | Low | Medium |
Timedifferent | 60-120 min | Mehrere Wochen | 1-5 Tage | 45-60 min |
Participantsdifferent | 2-8 | 2-6 researchers plus sample | Nutzertraffic | 2-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Interest Metrics, Conversion Signal, Learning Note | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | OutcomesInnovationResearchQuantitative | ValidationExperimentsDemandGrowth | AssumptionsRiskExperimentsValidation |