View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Systems Thinking Evaporating Cloud |  Delivery Value Stream Mapping |
|---|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | Ongoing | 60-120 min | 1-3 h |
Participantsdifferent | 2-12 | 2-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | FlowVisual managementDelivery | Theory of ConstraintsAssumptionsSystems thinking | LeanFlowWasteDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
