What are the Key Takeaways from this Executive Summary?
Quick answer
- The obvious cause is usually not the cause. Late deliveries blamed on carriers often trace back to dock scheduling. Write-offs blamed on the warehouse often start in the forecast.
- Four methods, four jobs. The 5 Whys drills one thread. Fishbone widens the search. Pareto ranks what to fix. Fault Tree Analysis handles compound failures.
- The bottleneck is data access, not analysis. Most investigations spend their time waiting for figures from another department. That wait is measurable, and it is the thing to measure first.
Why Do Supply Chain Teams Keep Fighting the Same Fires?
Quick answer
Every VP of Supply Chain Operations knows the pattern. A shipment misses its window. The team expedites a replacement, files a carrier complaint and moves on. Three weeks later it happens again — different lane, different item, same outcome. Last time’s corrective action report is still open.
The problem is not effort. It is depth. When on-time delivery dips, the instinct is to blame the visible actor: the carrier was late, the warehouse shorted the order, the supplier shipped bad material. Those explanations are rarely wrong. They are rarely complete either. The carrier was late because the trailer waited four hours for a door. The warehouse shorted the order because the stock count was out of date. The supplier shipped bad material because a spec change never reached their quality team.
Root cause analysis is the discipline of not stopping at the first plausible answer.
How Does the 5 Whys Method Work in Supply Chain?
Quick answer
The 5 Whys looks trivial and is not. The power is not in the number five; it is in refusing to stop at the first answer that satisfies the room.
Take a distribution centre that keeps missing same-day cut-offs on Tuesdays.
- Why are Tuesday orders shipping late? Pick waves are not finishing before the carrier cut-off.
- Why are pick waves late? Inbound receiving is using all the available labour until mid-afternoon.
- Why does receiving run so long on Tuesdays? Three major suppliers all deliver on Tuesday morning.
- Why do three suppliers deliver on the same day? Purchase orders were consolidated to cut inbound freight cost.
- Why did nobody check dock capacity? The procurement team’s transport system and the warehouse’s appointment calendar do not share data.
The cause is not slow picking. It is that inbound buying and dock scheduling cannot see each other. No amount of overtime or carrier penalties touches it.
What Is the Fishbone Diagram and How Does It Apply to Logistics?
Quick answer
Where the 5 Whys follows one thread, the Fishbone maps the whole field. For a logistics leader looking at repeated inventory write-offs, the six branches force six different questions:
- People: are planners overriding the forecast upwards as a habit?
- Process: does the S&OP cycle use sell-through, or only sell-in?
- Technology: is the planning system running on stale history with no current market signal?
- Materials: do some items have shelf-life limits that make them obsolete faster?
- Environment: did a seasonal or regulatory change make certain stock unsellable?
- Measurement: is forecast accuracy measured finely enough to show bias at item level?
In the case above, the write-offs were first put down to warehouse handling — poor rotation, damage, miscounts. The Fishbone search found something else: the forecast ran high as a matter of course, and the planning cycle rewarded commercial optimism over stock accuracy. The warehouse was managing the consequences of a decision made upstream.
How Does Pareto Analysis Prioritize Which Root Causes to Fix First?
Quick answer
Once a team has several candidate causes, the question changes from “what is broken” to “what do we fix first”. Pareto analysis answers it by putting a cost against each.
The method is concrete. Take a year of accessorial invoices, attribute each charge to the cause behind it, and sort the causes by total spend. A mid-market 3PL looking at rising demurrage and detention might list fifteen contributing causes, and find that a handful of them — dock appointment no-shows, missing documentation, chassis shortages — account for most of the money, while the rest are real but marginal. The ranking will be specific to that operation, which is the point: it is built from its own invoices rather than from a benchmark.
That ranking is what makes a finite improvement budget go somewhere useful. Fixing everything at once is neither possible nor necessary.
When Should Supply Chain Teams Use Fault Tree Analysis?
Quick answer
Not every failure is a chain. Some only happen when several safeguards fail together. Fault Tree Analysis maps that with AND and OR gates.
Take a serious On-Time In-Full miss at a retail distribution centre. It might need all three of the following: the primary carrier missed the pickup (either a driver shortage or a dispatch error), the backup carrier was never triggered (the alert rule had been switched off during an update), and the customer’s dock closed early for a holiday the order system did not know about.
No single failure caused the miss. The value of the method is that it shows which single safeguard, restored, would have prevented it regardless of the others.
How Does Cross-System Reading Speed Up Root Cause Analysis?
Quick answer
The limiting factor in root cause work is rarely analytical skill. It is data access. Tracing one late delivery back to a dock conflict means records from the transport system, the yard system, the carrier’s tracking and the warehouse appointment calendar. In most organisations that means emails, spreadsheet exports and a week of back-and-forth between departments.
That is the bottleneck Runink FACE addresses: it reads records across systems that were never built to talk to each other, so carrier transit times, dock dwell, appointment adherence and upstream purchase-order timing can be compared against each other rather than requested department by department. What comes out is the set of records that differ from the rule governing them, named individually. Deciding which of those is the root cause is still an analyst’s judgement; what changes is that the analyst starts with the records rather than with an email thread.
This is not about replacing a Continuous Improvement Manager’s expertise. It is about that expertise starting from the whole picture rather than from whichever system one department happens to own. The sharpest questions are still the analyst’s to ask.
Conclusion
Quick answer
The 5 Whys for a single thread. Fishbone for a wide search. Pareto for deciding the order. Fault Tree Analysis for compound failures. These are not theoretical frameworks; they are the working tools of operations that stop having the same meeting every quarter.
The difference between organisations that solve a problem once and ones that solve it repeatedly is not talent. It is tooling and discipline. A reasonable first measure, before any tool is bought: count how many working days your last three investigations spent waiting for data from another department. That figure is the size of the problem, and it belongs to your operation. Get in touch if it would help to work through it.
Sources
- ASQ — Root Cause Analysis Resources — The American Society for Quality’s own descriptions of the 5 Whys and Fishbone methods
- ASCM (APICS) — Continuous Improvement — Practitioner standards for continuous improvement in supply chain operations
- MIT Sloan Management Review — Management research on supply chain resilience and operational problem-solving
- Council of Supply Chain Management Professionals (CSCMP) — Industry glossary and definitions for the logistics measures used above
