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 |  Delivery Value Stream Mapping |  Product Discovery Assumption Mapping |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 60-120 min | 1-3 h | 45-60 min | 1-4 Wochen |
Participantsdifferent | 2-8 | 4-10 | 2-8 | 1-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Current-state map, Future-state map, Bottleneck list | Assumption map, Test backlog, Risk ranking | Experiment results, Decision log, Learning summary |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | LeanFlowWasteDelivery | AssumptionsRiskExperimentsValidation | ExperimentsGrowthAnalyticsValidation |