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 | ![]() Engineering Kanban | ![]() Systems Thinking Current Reality Tree | ![]() Operations Bottleneck Analysis |
|---|---|---|---|---|
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. | 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. | A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once. | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 h | Ongoing | 2-6 h | 1-3 h |
Participantsdifferent | 4-10 | 2-12 | 3-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics | Current Reality Tree, Core Problems, Intervention Ideas | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | LeanFlowWasteDelivery | FlowVisual managementDelivery | Systems thinkingRoot causeConstraintsCausality | FlowMeasurementConstraints |



