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 |  Engineering Kanban |  Systems Thinking Theory of Constraints Thinking Process |
|---|---|---|---|---|
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 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 Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 60-120 min | 1-3 h | Ongoing | 0.5-3 Tage |
Participantsdifferent | 2-8 | 4-10 | 2-12 | 4-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | LeanFlowWasteDelivery | FlowVisual managementDelivery | Theory of ConstraintsConstraintsSystems thinkingCausality |