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 |  Delivery Shape Up |  Operations Barrier Analysis |  Operations Causal Factor 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. | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | 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 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | Ongoing | 6 Wochen Cycle + 2 Wochen Cool-Down | 2-4 h | 2-6 h |
Participantsdifferent | 2-12 | 2-4 pro Pitch | 2-6 | 3-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions |
Tagsno overlap | FlowVisual managementDelivery | PlanningDeliveryAutonomy | Root causeSafetyIncident | CausalityIncidentRoot causeTimeline |