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 Leverage Points |  Delivery Value Stream Mapping |  Systems Thinking Intervention 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. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | Ongoing | Half day | 1-3 h | 1-5 Tage |
Participantsdifferent | 2-12 | 3-12 | 4-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Leverage Map, Action Strategy | Current-state map, Future-state map, Bottleneck list | Logic Model, Change Objectives, Intervention Components, Evaluation Plan |
Tagsno overlap | FlowVisual managementDelivery | Systems thinkingChangeStrategy | LeanFlowWasteDelivery | ChangeSystems thinkingCapability |