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 |  Systems Thinking Evaporating Cloud |  Innovation Design Thinking |  Systems Thinking Future Reality Tree |
|---|---|---|---|---|
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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 30-60 min je Interview | 60-120 min | 1 Tag bis mehrere Wochen | 2-4 h |
Participantsdifferent | 5-10 Interviews | 2-8 | 4-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Problem Statement, Prototype, Test Learnings | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | ValidationInterviewsPrototype | Theory of ConstraintsAssumptionsSystems thinking | InnovationPrototypeResearch | Theory of ConstraintsSystems thinkingChange |