The Constraints on Value Creation in Procurement

It is easy to write encouragingly about value creation and harder to be honest about why it so often does not happen. Functions that genuinely want to move beyond savings, that have capable people and a sensible strategy, still find their value ambitions thinning out over the year until what remains is mostly the price reductions they were already doing. This is not a failure of will or of talent. It is the predictable result of a set of structural constraints, and a piece that pretended these constraints away in favour of a motivational message would be worth nothing. The cornerstone of this series located the bottleneck in conversations and relationships. The constraints below are the specific forces that make those conversations hard to have or easy to avoid.

The scorecard only counts one kind of value

The first and heaviest constraint is measurement. Most procurement functions are measured on savings, often a single negotiated-savings number reported to finance, and what gets measured is what gets done. A buyer who spends three weeks shaping a requirement or brokering a supplier-innovation conversation has created real value and has nothing to put in the column that determines how their performance is judged. The savings number is not wrong, but as the dominant metric it actively pulls effort toward the one lever that is easy to count and away from the levers that are not. Until a function can credibly measure non-savings value, the scorecard will keep quietly overruling the strategy, and our piece on measuring negotiation performance rather than just outcomes is the companion to this point.

Procurement arrives after the decisions are made

The second constraint is timing, and it is structural rather than personal. A great deal of value is determined upstream, when requirements are formed and specifications written, and procurement is frequently brought in only once those decisions are settled and the task has narrowed to getting a price. The piece on the specification that arrives too late describes one version of this; the general form is that the function is positioned as a late-stage processor rather than an early-stage shaper. You cannot shape demand you are shown only after it has hardened, and you cannot broker a supplier relationship for a decision that has already been made. Late involvement does not reduce value creation at the margin. It removes whole categories of it.

No mandate to challenge the business

The third constraint is authority, or the lack of it. Several of the largest value levers require procurement to challenge the business: to question whether a requirement is genuinely needed, whether a preferred supplier is really the right one, whether a specification is gold-plated. Doing that requires a mandate the function often does not have, formally or culturally. Where procurement is seen as a service function that executes the business's decisions, challenging those decisions reads as overstepping, and a buyer who does it once without standing may not be invited back. The mandate to challenge is earned, and until it is, the most valuable conversations are also the most politically costly ones to start.

Stakeholders route around the obstacle

The fourth constraint follows from the third. When procurement is experienced as a source of friction rather than help, the business learns to route around it: to engage suppliers directly, to present procurement with a done deal, to treat involvement as a compliance step to be minimised. Every such workaround removes procurement from exactly the conversations where value is created. This constraint is self-reinforcing, because the less the function is involved, the less it can demonstrate the value of involvement, and the more reasonable the routing-around looks. Breaking the cycle is less about process mandates than about becoming useful enough that the business chooses to involve procurement, which is slow, relational work.

The value that cannot be seen cannot be defended

The final constraint is visibility. Savings are legible to finance; avoided risk, released working capital, and accessed innovation often are not, or are attributed elsewhere. Value that cannot be seen cannot be defended at budget time, cannot be used to justify the headcount that would create more of it, and cannot build the function's reputation. This is not only a measurement problem but a narrative one: procurement frequently lacks the means, and sometimes the inclination, to make its non-savings value visible to the people who decide its mandate. The result is a function that may be creating value it gets no credit for, which over time erodes the very standing it would need to create more.

What follows from naming them

These constraints are real, and pretending otherwise helps no one. But naming them precisely is the first step to working within or against them, because each one points at a response. The scorecard problem points at better measurement. The timing problem points at earning earlier involvement. The mandate, routing, and visibility problems all point back at the same thing: the function's standing with the business, which is built conversation by conversation over time. That is the uncomfortable convergence of this series. Almost every structural constraint on value creation is ultimately loosened by procurement being more trusted, more useful, and more persuasive in its dealings with its own organisation, and those are capabilities that can be deliberately built rather than waited for. Voice2Evolve is built to develop exactly that, so the constraints become things a function works on rather than excuses it lives with.