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 Systems Mapping |  Product Discovery Smoke Test |  Systems Thinking Future Reality Tree |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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. | 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 | Low | High |
Timedifferent | 60-120 min | 1-3 h | 1-5 Tage | 2-4 h |
Participantsdifferent | 2-8 | 3-12 | Nutzertraffic | 3-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | System Map, Dependencies, Leverage Points | Interest Metrics, Conversion Signal, Learning Note | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Systems thinkingMappingBoundariesChange | ValidationExperimentsDemandGrowth | Theory of ConstraintsSystems thinkingChange |