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 Causal Factor Analysis |  Operations Barrier Analysis |  Operations Family Tree 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 an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | Ongoing | 2-6 h | 2-4 h | 2-4 h |
Participantsdifferent | 2-12 | 3-10 | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | FlowVisual managementDelivery | CausalityIncidentRoot causeTimeline | Root causeSafetyIncident | Root causePatternsIncidentSystemic |