Learning objectives
- Translate symptoms (stockouts, expedites, inventory bloat) into root causes using a diagnostic framework.
- Compute a baseline of working-capital and service performance that the transformation will improve.
- Identify the small set of high-leverage issues that a transformation can realistically address.
Why Diagnostics Come First
Most supply chain transformations fail not because the strategy is wrong but because the diagnostic is shallow. Teams rush to a target operating model (a planning platform, a new network, a new S&OP cadence) before understanding why the chain is under-performing. The result is a tool that automates a broken process or a new structure that solves a non-existent problem. A good diagnostic answers three questions. First, where is the pain? Stockouts at which SKU/customer combinations, expedites at which lanes, excess inventory at which stages, missed forecasts at which categories. Second, why is the pain there? Demand variability, lead-time variability, misalignment between forecast and capacity, weak supplier performance, misalignment between commercial policy and supply policy. Third, what is the magnitude? Working-capital tied up, revenue at risk, expedite freight as share of total, customer-service credit notes. Without a quantified baseline, the business case is rhetorical; without a root-cause map, the program is a tool deployment. A useful diagnostic is small enough to finish in eight to twelve weeks, large enough to engage the leadership team, and quantitative enough to anchor the business case.
Quantifying the Baseline
Three numbers anchor most supply chain transformations. Working-capital tied up in inventory: average inventory value, decomposed by stage (raw, WIP, finished), by region, and by SKU health (fast/medium/slow). Excess-and-obsolete inventory: inventory past its sale window, plus inventory whose carrying cost exceeds its recoverable value. Service performance: fill rate, on-time-in-full, and stockout frequency, broken down by customer tier and product category. The baseline also includes the operational 'tax' paid for current performance: expedite freight as share of total freight, premium overtime as share of total labor, premium transportation as share of total logistics. These taxes are large in many chains and are the most credible source of savings; they are also the most credible proof that the transformation is working when they fall. The discipline is to publish a single page that shows the baseline and the cost of staying where you are. Without that page, transformation debates are arguments about feelings; with it, they are arguments about money.
Picking the Few Issues That Matter
A diagnostic almost always reveals more problems than the company can address. The transformation cannot fix everything; it must pick the few issues that drive most of the cost. A useful exercise: rank issues by (a) annual cost of the pain and (b) plausibility that a 12–24 month program can move them. The first few items on that ranking are the program's targets. Common high-leverage issues in mid-cap manufacturers: SKU proliferation (too many SKUs per plant), forecast bias (systematic over- or under-forecast at the category level), S&OP that does not actually make decisions, supplier concentration with no qualified second source, inventory held at the wrong stage (WIP upstream of long changeovers, finished goods upstream of stable demand), planning tooling that runs but is not trusted. The list is rarely glamorous; the value comes from addressing a few items deeply rather than spreading thin across twenty. The program charter should name the five issues it will fix and explicitly say which ones it will not.
Worked example
Problem
A mid-cap precision-parts manufacturer reports annual COGS of $220M, $96M average inventory, $4.2M annual expedite freight on a $15M total freight spend, fill rate 91% against a 96% target on Tier-1 customers, and $6.8M of excess-and-obsolete (E&O) inventory. Contribution margin is 35% and the holding rate is 22%. Management's own internal target for expedite share, set from the two best-performing plants, is 8%. Build the baseline: inventory days of supply, expedite share, and a savings envelope. Take care not to double-count overlapping inventory savings, and separate revenue protected from profit earned.
Step by step
- Inventory days of supply = (average inventory / COGS) × 365 = (96 / 220) × 365 = 159 days.
- Expedite share = $4.2M / $15M = 28.0%. Against the internal 8% target, avoidable expedite ≈ (0.28 − 0.08) × $15M = $3.0M/year. Note that 8% is this company's own best-plant performance, not an industry benchmark; published cross-industry expedite benchmarks vary so widely with product mix and network design that an internally derived target is the more defensible anchor.
- Fill-rate gap = 96% − 91% = 5 percentage points. At $3.5M of revenue protected per point, that is $17.5M of revenue at risk. Convert to profit before claiming it: 35% contribution margin gives $6.1M/year. Two cautions. This is contribution, not operating profit, since it does not carry fixed costs. And it is revenue protected rather than won, so it only materialises if those customers would otherwise have taken the volume elsewhere permanently.
- E&O carrying cost = 22% × $6.8M = $1.5M/year. Halving the E&O balance saves $0.75M/year of carrying cost.
- Inventory reduction: assume 10% of the $96M base is removable through stage-of-build changes and SKU rationalisation, giving $9.6M of one-time working-capital release and 22% × $9.6M = $2.1M/year of carrying cost.
- Now remove the double count. The $6.8M of E&O sits inside the $96M inventory base, so the E&O reduction of $3.4M is part of the $9.6M reduction, not additional to it. Counting both the $0.75M and the full $2.1M charges the same inventory twice. Netting E&O out, the non-E&O reduction is $9.6M − $3.4M = $6.2M, worth 22% × $6.2M = $1.36M/year, which added to the $0.75M E&O saving gives $2.1M/year total — the same figure, correctly derived once.
- Corrected savings envelope: $3.0M (expedite) + $6.1M (fill-rate contribution) + $2.1M (inventory carrying, E&O included) = $11.2M/year run-rate, plus a $9.6M one-time working-capital release.
Answer. Inventory ≈ 159 days of supply. Expedite share is 28% against an internal 8% target, implying ≈ $3.0M/year of avoidable expedite. Closing the 5-point fill-rate gap protects $17.5M of revenue, worth ≈ $6.1M of contribution. Inventory work is worth ≈ $2.1M/year of carrying cost plus a $9.6M one-time release. Total run-rate envelope ≈ $11.2M/year. The naive sum of the four line items comes to $11.95M, and the $0.75M difference is the E&O saving double-counted inside the broader inventory reduction; counting the same saving twice inflates the business case. Treat $11.2M as an envelope rather than a target: the fill-rate line is over half of it and rests on the least verifiable assumption in the set, so sensitivity-test it at 50% realisation before anyone commits to a number.
Practice
Work each question before opening the solution.
-
What three numbers typically anchor a supply chain transformation business case?
Show solution for question 1
Working-capital tied up in inventory, expedite and premium-cost share of operating spend, and service performance (fill rate or on-time-in-full). These translate pain into dollars and create a baseline the program can be measured against.
-
Why is 'expedite share of freight' a useful diagnostic metric, and where should the comparison threshold come from?
Show solution for question 2
It converts an operational shortfall into a number finance already tracks. When buffer, capacity, or supplier reliability falls short, someone books premium freight to protect the customer, so service metrics can stay green while the cost migrates quietly onto the freight line. A rising share means the chain is structurally running hot. The threshold should come from inside the company wherever possible: the best-performing plant, region, or product family, or the company's own history before performance degraded. Published cross-industry figures vary so much with product mix, network density, and how each firm classifies premium freight that comparing against them invites an argument about definitions rather than a conversation about the gap.
-
Why should a transformation pick a few issues to fix deeply rather than spread across many?
Show solution for question 3
Because organizational attention and change-management bandwidth are limited; spreading thin rarely moves any metric meaningfully. Concentrated effort on a few high-leverage issues produces measurable improvement and builds credibility for the next phase.