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 |  Agile Ideal Days |  Systems Thinking Future Reality Tree |
|---|---|---|---|---|
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 effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | Ongoing | Half day | 15-60 min | 2-4 h |
Participantsdifferent | 2-12 | 3-12 | 2-9 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Leverage Map, Action Strategy | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | FlowVisual managementDelivery | Systems thinkingChangeStrategy | EstimationEffortAgile | Theory of ConstraintsSystems thinkingChange |