Why "buy better software" so often fails to fix supply chain problems
A recurring pattern in supply chain improvement projects is that a business invests in new planning software, expects the tool itself to fix coordination problems between departments, and is disappointed when the underlying friction persists largely unchanged. This is a genuinely common and well-documented failure mode, and the reason is straightforward once named: software can make information easier to share and calculations faster to run (see how planning software actually optimises for more on what these tools can and cannot do), but it cannot, on its own, change who is accountable for an end-to-end outcome, or realign incentives that are currently pulling different departments in different directions. A tool that surfaces a demand-supply mismatch clearly to everyone in the business is still not useful if no one has the authority, or the incentive, to act on what it shows.
This is why supply chain integration is, at its core, an organisational design problem as much as a technical or process one. The technical and process pieces — better forecasting, a shared Sales & Operations Planning cadence, cleaner data — are necessary, but they tend to under-deliver when the underlying organisational structure and incentives are still set up to reward local, functional performance over shared, end-to-end performance.
The classic silo problem, and why it is so persistent
The conventional functional organisation — separate sales, operations, procurement and finance departments, each with its own leadership, budget and performance targets — exists for good reasons: it allows genuine specialisation and clear individual accountability within each function. The problem is that a customer order, or a supplier shipment, does not respect those functional boundaries; it flows through sales, planning, procurement, warehousing and finance in sequence, and each functional handover is a point where local optimisation can quietly work against the end-to-end outcome.
| Function | Typical local incentive | Consequence for the whole chain |
|---|---|---|
| Sales | Maximise revenue and never lose a sale to a stock-out | Pressure to over-forecast and over-stock, inflating inventory |
| Finance | Minimise working capital tied up in inventory | Pressure to under-stock, risking availability and service |
| Operations/procurement | Minimise unit cost and cost-per-shipment | Pressure to order in large batches, which conflicts with both of the above |
None of these three functional instincts is unreasonable on its own terms — each is a rational response to how that function is measured. The problem is structural: without some mechanism that forces these competing local optimisations to be reconciled against a single, shared end-to-end goal, the business ends up with an outcome that satisfies no one's actual interests particularly well, including the shareholders funding the working capital these unresolved conflicts consume.
Starting with a vision, not a reorganisation chart
A common mistake in tackling this problem is to jump straight to restructuring — creating a new department, appointing a new head of supply chain, redrawing the org chart — before anyone in the business has articulated, in plain terms, why integration actually matters and what it is meant to achieve. Restructuring without that shared understanding tends to produce a reorganisation in name only: the boxes on the chart change, but the underlying incentives, habits and working relationships often persist largely unchanged beneath the new labels.
A more durable starting point is a clearly articulated vision — leadership explicitly naming the specific business outcome integration is meant to deliver (for example, "we lose sales to stock-outs on our top twenty products roughly a fifth of the time, and we believe better cross-functional planning could meaningfully reduce that") and using that concrete, shared problem statement to build genuine buy-in across the functions that will need to change how they work. A vision framed this way gives people a reason to accept some loss of local autonomy in service of a goal they can see and believe in, which tends to succeed far more often than a structural change imposed with only a vague, unstated rationale behind it.
Practical organisational responses
Once the case for change is genuinely shared, a handful of concrete organisational levers tend to do most of the practical work.
- Explicit end-to-end process ownership — naming a single person or small team accountable for the whole order-to-delivery outcome, not just one functional segment of it, so that cross-functional trade-offs have somewhere to be resolved rather than being silently absorbed at whichever handover point happens to be weakest.
- Shared, not purely functional, incentives — tying at least part of each function's performance measurement to a shared cross-functional metric (an overall OTIF or working-capital target, for instance), so that sales, finance and operations have some genuine stake in each other's outcomes rather than being rewarded purely for optimising in isolation.
- A regular cross-functional forum — a recurring, structured meeting cadence (this is exactly what a well-run S&OP process provides) where competing functional views are surfaced and reconciled on a fixed schedule, rather than only being addressed reactively when a conflict becomes visible and urgent.
- Phased, pilot-based change — testing a new cross-functional way of working on one product category or region before rolling it out business-wide, which builds credible evidence and champions for the change rather than asking the whole organisation to adopt an unproven new model all at once.
Benchmarking against comparable organisations — including using a structured framework like SCOR to compare specific process categories — is also a genuinely useful tool for building urgency: showing leadership and functional heads a concrete performance gap against peers tends to be considerably more persuasive than an abstract argument that "we should integrate better," because it turns the case for change into a measurable target rather than a vague aspiration.
A South African example: growing past the owner-run stage
A pattern that shows up repeatedly among South African importers and distributors is the transition from a small, owner-run operation — where one or two people effectively hold the whole picture in their heads and can informally reconcile sales, stock and cash-flow decisions on the fly — to a larger business where sales, warehousing and finance are run by different people with genuinely different day-to-day priorities. In the owner-run phase, integration is effectively free: there is no silo problem because there is no silo. Once the business grows past that point, the same coordination that used to happen informally, in one person's head, now has to be deliberately designed into a process — and businesses that don't make that transition explicitly often find that growth itself is what exposes and worsens the classic sales-versus-finance-versus-operations tension described above, precisely at the point where the stakes (larger overseas orders, longer lead times, more working capital at risk) are highest.
Recognising this transition early — and building a lightweight cross-functional planning rhythm before the informal, one-person coordination model breaks down under its own growth — tends to be considerably less painful than waiting until a visible failure (a large stock-out, or a costly excess-inventory write-off) forces the issue.
Frequently asked questions
If new planning software doesn't fix organisational silos on its own, is it still worth investing in?
Generally yes, but expectations matter. Software can make cross-functional information genuinely visible and shared, which is a necessary precondition for better coordination — but it works best when introduced alongside the organisational changes (shared incentives, clear process ownership) described here, not as a substitute for them.
Do we need to create a formal "Head of Supply Chain" role to fix this?
Not necessarily, particularly for a smaller business. What matters more than the specific title is that someone is genuinely accountable for the end-to-end outcome rather than just one functional slice of it. In a smaller organisation this can be a shared responsibility exercised through a regular cross-functional meeting rather than a dedicated new executive role.
Why start with a vision instead of just restructuring directly?
A restructuring imposed without a shared, understood rationale tends to change the org chart without changing the underlying incentives and habits driving people's day-to-day decisions. A clearly articulated vision builds the buy-in needed for people to genuinely accept new ways of working, rather than quietly reverting to old patterns once attention moves elsewhere.
How is this different from just running a good S&OP process?
S&OP is one of the practical mechanisms that supports integration — a recurring forum where cross-functional trade-offs are surfaced and reconciled. But S&OP alone can struggle if the underlying incentives still reward purely functional performance; the organisational-design work described here (shared incentives, clear ownership) is what makes a good S&OP process sustainable rather than a meeting people attend but don't act on.
At what size of business does this become a real problem?
There is no fixed threshold, but the transition tends to become visible once a business grows beyond the point where one or two people can informally hold the whole picture in their heads and reconcile sales, stock and cash-flow decisions on the fly. Beyond that point, coordination generally has to be deliberately designed rather than left to happen informally.