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 |  Product Strategy Impact Mapping |  Decision Making Constraint Analysis |  Operations Bottleneck Analysis |
|---|---|---|---|---|
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. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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 | Low | Medium |
Timedifferent | Ongoing | 45-90 min | 30-90 min | 1-3 h |
Participantsdifferent | 2-12 | 3-8 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Impact Map, Outcome Hypotheses, Delivery Options | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | FlowVisual managementDelivery | OutcomesStrategyBehaviorPlanning | ConstraintsDecisionPlanningOptions | FlowMeasurementConstraints |