View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Bottleneck Analysis |  Engineering Kanban |  Systems Thinking Iceberg Model |  Systems Thinking Current Reality Tree |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 h | Ongoing | 30-60 min | 2-6 h |
Participantsdifferent | 3-8 | 2-12 | 2-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Kanban board, WIP policies, Flow metrics | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Current Reality Tree, Core Problems, Intervention Ideas |
Tagsno overlap | FlowMeasurementConstraints | FlowVisual managementDelivery | Systems thinkingRoot causePatterns | Systems thinkingRoot causeConstraintsCausality |