A supply chain programme can succeed on both halves and still fail as a whole. Strategy stops at the concept. System integration starts at the scope. Between them sits the question neither one answers: how this supply chain is actually steered. That question belongs to nobody, and it is where performance is won or lost.
Christian Kroschl · Twenty years in pharma and manufacturing networks
A manufacturer runs two programmes back to back. A strategy firm designs the target operating model: capability map, governance model, a roadmap in three waves. Solid work, signed off by the board. A system integrator then delivers the planning platform: scope agreed, data migrated, users trained, go live on schedule.
Eighteen months after go live, service performance sits where it sat before. Inventory is slightly higher. The planners maintain a set of spreadsheets alongside the new system, and the weekly escalation call is still the place where the real priorities get set.
Nobody failed. Both firms delivered exactly what they contracted to deliver. That is the part worth looking at.
The consulting market for supply chain work is split, and each half is internally coherent.
Strategy work ends at the concept. The artefacts are familiar: an operating model, a capability map, a governance design, a roadmap, a business case. They are useful, and they stop at exactly the point where the interesting questions begin, because the next layer down does not fit on a slide and does not survive a steering committee.
Notice what that sentence does not say. The problem is not the artefacts. An operating model is precisely the right object to build. The problem is where it is allowed to end.
System integration begins at the scope. It takes a defined solution design and makes it exist: modules, configuration, interfaces, data migration, cutover, hypercare. Also useful, and it starts from an assumption that somebody upstream has already decided what the system is supposed to do.
Neither half is wrong. Together they are incomplete, and the incompleteness has a specific address.
Between the concept and the configuration sits a body of decisions that neither side owns. Not because either is negligent, but because these decisions are too detailed for the strategy phase and too consequential to be made during configuration. They fall through, and they get made anyway, by whoever is closest to the keyboard when the field needs a value.
There is a reflex to file all of this under planning, and it is worth resisting.
Planning and control is where the gap becomes visible first. It is the layer that produces a number every week, so it is the layer where the absence of a decision shows up as a missed date. That is why most of the examples below are drawn from there.
It is not the boundary of the problem. Steering a supply chain spans the planning and control mechanism, the execution feedback that tells you whether the plan survived contact with the floor, the data model everything rests on, the system architecture that has to carry the decisions, the operating model and the governance that assigns them, the analytics and increasingly the AI layered on top, and whether any of it is adopted by the people who have to run it on a Tuesday morning.
Treat those as separate workstreams with separate owners and separate vendors and you do not remove the gap. You multiply it. Every seam between them becomes a smaller copy of the same problem.
The question is not who plans. The question is how this supply chain is steered, end to end, and who is accountable for the answer.