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 | ![]() Innovation Lean Startup | ![]() Product Strategy Lean Canvas |
|---|---|---|---|---|
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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 60-120 min | Wochen bis Monate je Lernzyklus | 45-90 min |
Participantsdifferent | 4-10 | 2-8 | 2-8 | 1-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Lean Canvas, Core Assumptions, Experiment Backlog |
Tagsno overlap | LeanFlowWasteDelivery | Theory of ConstraintsAssumptionsSystems thinking | LeanStartupValidationMVP | StartupLeanAssumptionsBusiness model |



