View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Force Field Analysis | ![]() Engineering Kanban | ![]() Systems Thinking Leverage Points | ![]() Delivery Cost of Delay |
|---|---|---|---|---|
Purposedifferent | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | Low | Medium | High | High |
Timedifferent | 45-90 min | Ongoing | Half day | 90-180 min |
Participantsdifferent | 3-12 | 2-12 | 3-12 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Kanban board, WIP policies, Flow metrics | Leverage Map, Action Strategy | CoD Table, Prioritization Sequence |
Tagsno overlap | ChangeDecisionStrategy | FlowVisual managementDelivery | Systems thinkingChangeStrategy | PrioritizationDeliveryEconomicsDecision |



