Most senior decision-makers backing a supply chain transformation are working from a business case built entirely by the people who want it approved. That is a structural problem, not a failure of trust.
You are not a supply chain expert. That is not a gap — it is the normal condition of a senior decision-maker or budget holder in any large organisation. Your supply chain director or VP is the expert. The question is whether their expertise, applied to a decision this significant, is sufficient on its own — or whether the people building the case are also the people least well placed to spot its weaknesses.
The gap that consistently produces poor outcomes in supply chain transformation is not between good and bad proposals. It is between proposals that have been genuinely stress-tested by independent, experienced people and proposals that have not. Most proposals reaching board or C-suite approval have been through extensive internal review. Very few have been through independent peer scrutiny by practitioners who have navigated comparable decisions and have no stake in the outcome.
The questions worth asking are not technical. They are structural: has the diagnosis been tested by anyone who does not work for this organisation? Has the operating model question been resolved before a vendor was selected? Does the maturity of the organisation match the ambition of the investment? And — most importantly — if the case is wrong in a way that matters, who would know?
These questions are not a sign of distrust in your team. They are the standard of rigour that significant capital commitments deserve — and that most organisations apply to every other class of major investment.
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 most useful thing a senior decision-maker can do before approving a significant supply chain investment is ensure the case has been stress-tested by people who are neither the internal team nor the vendors. Not to challenge the team's judgment, but to give their judgment something to push against.
Specifically: asking whether the diagnosis has been validated by practitioners who have navigated comparable decisions in comparable organisations; asking whether the operating model design preceded the technology selection or followed it; and asking what the realistic worst-case looks like — not the worst case in the risk register, but the worst case that experienced practitioners have actually seen in similar programmes.
The pre-commitment dinner format BPC is developing brings together senior decision-makers and supply chain leaders to work through exactly these questions before capital is committed. It is designed for the moment after the business case is broadly formed but before formal approval is sought — when the cost of finding a problem is low and the cost of missing one is high.
An intimate dinner for senior decision-makers and budget holders the evening before Confidence Before Commitment, exploring what it takes to evaluate a supply chain transformation investment case with confidence.
A capability investment case that fails to survive contact with finance usually reflects a problem with how it was constructed. This session examines what investment decision-makers actually need — and how to build a case that holds up through a multi-year programme.