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 MORT 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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 | High | High |
Timedifferent | Ongoing | 6 Wochen Cycle + 2 Wochen Cool-Down | Mehrere Tage bis Wochen | 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 | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions |
Tagsno overlap | FlowVisual managementDelivery | PlanningDeliveryAutonomy | Root causeSafetySystemicIncident | CausalityIncidentRoot causeTimeline |