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 |  Operations Fault Tree Analysis |  Systems Thinking Current Reality Tree |  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. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | 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. | 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 | High | High | Medium |
Timedifferent | Ongoing | 2-6 h | 2-6 h | 1-3 h |
Participantsdifferent | 2-12 | 3-8 | 3-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Current Reality Tree, Core Problems, Intervention Ideas | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | FlowVisual managementDelivery | RiskRoot causeSafety | Systems thinkingRoot causeConstraintsCausality | FlowMeasurementConstraints |