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 Systems Mapping |  Systems Thinking Evaporating Cloud |  Product Discovery Fake Door Test |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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 | 1-3 h | 60-120 min | 1-5 Tage | 45-60 min |
Participantsdifferent | 3-12 | 2-8 | Nutzertraffic | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Click Data, Interest Signal, Learning Decision | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Systems thinkingMappingBoundariesChange | Theory of ConstraintsAssumptionsSystems thinking | ValidationExperimentsDemandDiscovery | AssumptionsRiskExperimentsValidation |