View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Design Thinking |  Product Discovery Solution Interview |  Systems Thinking Evaporating Cloud |  Product Discovery Outcome-Driven Innovation |
|---|---|---|---|---|
Purposedifferent | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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. | 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. |
Complexitydifferent | High | Medium | Medium | High |
Timedifferent | 1 Tag bis mehrere Wochen | 30-60 min je Interview | 60-120 min | Mehrere Wochen |
Participantsdifferent | 4-10 | 5-10 Interviews | 2-8 | 2-6 researchers plus sample |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Problem Statement, Prototype, Test Learnings | Solution Feedback, Objection List, Validation Notes | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses |
Tagsno overlap | InnovationPrototypeResearch | ValidationInterviewsPrototype | Theory of ConstraintsAssumptionsSystems thinking | OutcomesInnovationResearchQuantitative |