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 |  Systems Thinking System Dynamics Simulation |  Product Discovery Smoke Test |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | System Dynamics Simulation makes assumptions about time, delay, and feedback testable through experiments. It draws relationships, patterns, and feedback loops. The result is captured as a simulation model and scenario reports. | 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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 60-120 min | Mehrere Tage bis Wochen | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 2-8 | 1-5 Modellierende, Stakeholder asynchron | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop | Async | Async | Async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Simulation Model, Scenario Reports | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Systems thinkingDynamicsSimulationAnalysis | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |