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 Fishbone Diagram |  Engineering Kanban |  Operations 8D Problem Solving |
|---|---|---|---|
Purposedifferent | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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 acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 30-60 min | Ongoing | 1-6 Wochen |
Participantsdifferent | 2-8 | 2-12 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Kanban board, WIP policies, Flow metrics | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | Root causeQualityOperations | FlowVisual managementDelivery | QualityProblem solvingRoot cause |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
