The most consistent pattern is a business case that has been built to secure approval rather than to reflect what the investment will actually deliver. The change champion has worked hard on it, the internal team has reviewed it, and by the time it reaches the board or C-suite the case has a momentum of its own. The assumptions underneath it — about data readiness, operating model design, organisational capacity for change, and the realistic cost of implementation — have rarely been tested by anyone with the relevant experience and no stake in the answer.

A related pattern is the vocabulary gap. Supply chain transformation business cases tend to be written in the language of supply chain practitioners for an audience that thinks in financial and strategic terms. The translation work — connecting service levels, inventory turns, and planning maturity to margin, free cash flow, and competitive positioning — is often done incompletely. Decision-makers end up approving something they broadly believe in without fully understanding what they are committing to.

The third pattern is what happens after approval. Transformation programmes that stall or underdeliver rarely do so because the technology was wrong. They do so because the organisational conditions — change leadership, data foundations, stakeholder alignment, decision rights — were not in place before the investment was committed. By the time that becomes visible, the budget is spent and the credibility of everyone involved is on the line.

The assumption most senior decision-makers are operating on is that a well-constructed business case from a trusted internal team is a reliable basis for approving a significant supply chain investment. If the numbers work and the people presenting them are credible, the decision should be sound.

The structural problem with that assumption is that the people building the case are also the people least well placed to identify its weaknesses. The diagnosis has been tested internally, by people who share the same adapted assumptions, work from the same data, and have a stake in the programme proceeding. The operating model questions may not have been resolved before the vendor was selected. The maturity assessment may reflect aspiration rather than current state. None of this is visible in the business case document, and it rarely surfaces in an internal review.

The organisations where senior decision-makers catch these problems before commitment rather than after tend to share one characteristic: the case was exposed to independent peer scrutiny from practitioners with relevant experience and no commercial stake in the answer... before the budget was approved, while the cost of finding a problem was still low.

BPC's outside-in view on this pattern comes from practitioners who have scrutinised and approved comparable investment decisions. Tell us about your context and we can find the most relevant comparisons.