Value Creation in Procurement: What Not to Do

Most advice on creating value tells you what to do. This piece is about the opposite, because the failure modes of value creation are more common than the successes and a great deal of credibility is lost in them. The function that wants to be taken seriously as a value creator can do itself more good by avoiding the recognisable anti-patterns than by adding another initiative, since each of these mistakes quietly teaches the rest of the organisation to discount what procurement claims. The series thesis applies here too: every one of these failures is, at root, a conversation handled badly or a relationship spent carelessly.

Do not claim savings finance cannot find

The most damaging anti-pattern is the savings number that exists only in procurement's own reporting. The function negotiates a reduction against a list price, or a should-cost model, or last year's quote, books it as a saving, and presents it upward, while finance looks at the actual spend and sees no corresponding fall. Our piece on why procurement savings do not reach the P&L examines the mechanics, but the reputational damage is the point here. Once finance learns that procurement's savings do not reconcile to the accounts, every subsequent claim is discounted, including the real ones. A smaller number that finance can verify is worth more to the function's credibility than a larger one it cannot, and the temptation to inflate is the temptation to borrow against your own future believability.

Do not use partnership language without partnership substance

The word partnership is the most overused and least earned term in the procurement vocabulary. Calling a supplier relationship a partnership does not make it one, and our piece on when partnership is the wrong frame sets out the structural conditions a genuine partnership actually requires. The anti-pattern is invoking the language as a substitute for the substance: describing a transactional, asymmetric relationship in the warm vocabulary of collaboration because it sounds more strategic. Suppliers see through it immediately, stakeholders learn to distrust the function's read of its own relationships, and the word loses whatever meaning it had for the cases where it genuinely applies. Reserve the language for the relationships that meet the conditions, and describe the others accurately.

Do not chase every lever at once

The previous piece in this series mapped the value levers, and the temptation on seeing them laid out is to pursue all of them simultaneously. This is its own failure mode. A function that launches a total-cost programme, a payment-terms initiative, a supplier-innovation push, and a demand-shaping effort in the same quarter, across a team that is already running its day job, will execute all of them shallowly and finish none of them. Value creation rewards depth over breadth, because each lever depends on a sequence of conversations that has to be carried through to a result. Picking the two levers where the function has the standing and the access to actually win, and doing them properly, beats a portfolio of half-started ambitions that mostly serves to make the strategy deck look comprehensive.

Do not present value as a slide instead of a behaviour

A recurring confusion is between describing value and creating it. A well-built value-creation framework, a category strategy full of opportunity, a roadmap with workstreams and owners, all of these can exist in complete form while no value is actually captured, because the document is not the work. The work is the difficult conversation that the document points at, and the document is comfortable precisely because it is not that conversation. The anti-pattern is mistaking the comfortable artefact for the uncomfortable act, and the tell is a function that is always planning value creation and rarely able to point to a specific conversation in which a specific lever was captured. The slide is not the value. The exchange that the slide describes is the value, and only if someone actually has it.

Do not over-claim credit

The last anti-pattern is the most relationally expensive. When value is created jointly with the business, as most of it is, procurement claiming sole credit for the outcome is a fast way to ensure the business does not collaborate next time. The stakeholder who shaped the requirement, the engineer who accepted the broadened specification, the budget owner who agreed the terms trade, all of them notice when procurement reports the win as its own. Credit is a currency, and spending it greedily on this quarter's scorecard buys a reputation that costs the function its access to the next opportunity. The functions that create the most value over time are frequently generous with credit, because generosity with credit is what keeps them invited into the conversations where value is made.

The discipline of not

Avoiding these patterns is not a negative discipline but a positive one, because each avoided mistake protects the standing on which all future value depends. The connective tissue is trust: claiming unverifiable savings, misusing partnership language, and over-claiming credit all spend the same scarce resource, the organisation's willingness to believe and involve procurement. That resource is built and depleted in conversations, which is why the capability to handle those conversations well, honestly, and with judgment about what to claim and what to share is itself among the most valuable things a function can develop. Voice2Evolve is built to rehearse exactly those judgments, so that value creation is something a team does rather than something it performs.