View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Value Stream Mapping | ![]() Systems Thinking Evaporating Cloud | ![]() Growth A/B Testing | ![]() Product Discovery Riskiest Assumption Test |
|---|---|---|---|---|
Purposedifferent | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 h | 60-120 min | 1-4 Wochen | 1-2 Wochen pro Iteration |
Participantsdifferent | 4-10 | 2-8 | 1-6 | 2-6 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Experiment results, Decision log, Learning summary | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | LeanFlowWasteDelivery | Theory of ConstraintsAssumptionsSystems thinking | ExperimentsGrowthAnalyticsValidation | ExperimentsValidationDiscoveryAssumptions |



