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 Problem Interview |  Product Discovery Concierge MVP |  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. | 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. | When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. | 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 | 60-120 min | 30-60 min je Interview | 1-4 Wochen | 45-60 min |
Participantsdifferent | 2-8 | 5-12 Interviews | 3-10 Kunden | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Problem Evidence, Risk Notes, Customer Segments | Concierge Learnings, Service Blueprint, MVP Risks | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | DiscoveryInterviewsValidation | MVPValidationServiceDiscovery | AssumptionsRiskExperimentsValidation |