Procurement & Supplier Negotiation
The Shared Evaluation System You Do Not Have
May 20, 2026
Ask three departments how a shared supplier is performing and you will usually get three different answers. Engineering rates them on technical responsiveness and the quality of their problem-solving. Finance judges them on cost and payment behaviour. The business unit that depends on them cares about delivery and flexibility. Procurement weighs the commercials and the contract. Each function is looking at a different facet of the same supplier and scoring it on its own terms, and none of them is wrong, exactly. They are simply not looking at the same thing, and they have never agreed on what a good supplier even looks like. The supplier, meanwhile, understands this perfectly, and quietly plays the gaps, citing the delighted engineer to the frustrated buyer and the cost saving to the operations lead who is worried about reliability. A function that assesses its suppliers in four uncoordinated pieces cannot speak to any of them with one voice, because it does not have one.
This is one of the most common and least discussed failures in supplier relationship management, and the diagnosis is correct: most procurement functions genuinely lack a shared, simple, structured way to evaluate a supplier that the whole organisation stands behind. Without it, supplier management is a collection of departmental impressions, and the supplier manages the spaces between them better than the buyer manages the supplier. The fix is real and worth stating plainly. You need a shared evaluation system: one agreed framework, one set of weighted criteria, one assessment that engineering, finance, the business, and procurement all recognise as the organisation's view rather than their own corner of it. A function that builds this has taken a genuine step that most never take.
Why building it is the easy half
The trap is in believing that the system is the hard part, because it is not. A competent consultant can design a supplier evaluation framework in a fortnight. A tool can host it, weight the criteria, and produce a tidy composite score on a dashboard. The artefact is straightforward to produce, and the market is full of well-built versions of it. If having the framework were the same as having the alignment, the problem would already be solved everywhere, because the frameworks are not hard to come by.
What is hard, and what the framework quietly assumes has already happened, is getting engineering, finance, and the business to actually align behind one assessment. That means agreeing the weights, which is really agreeing whose priorities count for how much. It means each department accepting a composite score that sometimes contradicts its own view of the supplier, and subordinating its facet to a shared picture it does not fully control. The engineer who values a supplier's technical brilliance has to accept a score dragged down by that supplier's commercial behaviour. Finance has to accept that the cheapest supplier carries an operational risk that lowers their rating. None of that alignment lives in the document. It lives in a series of cross-functional conversations, and they are often contentious, because each department's view of the supplier reflects its own priorities, and giving ground on the assessment feels like giving ground on what it cares about.
The alignment is an internal negotiation
This is where the shared evaluation system turns out to be the output of something harder rather than a substitute for it. Getting engineering to accept that the supplier they love is a commercial liability, or persuading finance that the lowest bidder is an operational hazard, is an internal negotiation in every meaningful sense. It has parties with different interests, positions that have to move, and an agreement that has to hold afterward. Our piece on the internal negotiations that procurement has to win covers this territory directly, and the supplier evaluation system is one of its highest-stakes instances, because the assessment that emerges will govern how the whole organisation deals with that supplier.
A function that buys the tool and skips these conversations ends up in a familiar and slightly worse place. It now has a beautiful shared framework that each department privately disagrees with, complies with on paper, and ignores in practice, continuing to deal with the supplier from its own unreconciled view. That is arguably worse than having no system, because it creates the appearance of alignment without the substance, and the supplier still plays the same gaps, now hidden behind an agreed score that nobody actually believes. The system only delivers its value when the alignment behind it is real, and the alignment is built in conversations, not in software.
And then the score only sets up the supplier conversation
There is a second conversation waiting beyond the internal one. Suppose the alignment holds and the organisation arrives at a single, credible assessment of the supplier. That assessment does not manage the supplier. It tells the buyer what to say. Conveying it to the supplier in a way that actually changes their behaviour, holding the agreed line when their account manager disputes the score, and converting a unified evaluation into a different relationship, is the supplier-facing conversation the whole system exists to set up. The score is the ammunition. The conversation is the act. This is the thesis the whole series has been building, and the evaluation system is a particularly clear case of it: the artefact surfaces and structures the conversation it cannot conduct.
So the shared evaluation system is genuinely necessary, and a function without one should build it. But it is worth being honest about where the difficulty actually sits, because it is not in the framework. It is in the cross-functional conversations that produce a real alignment rather than a paper one, and in the supplier conversations that turn an agreed assessment into a changed relationship. Both are capabilities rather than documents, and both are exactly what Voice2Evolve lets a procurement team rehearse: the internal negotiation that gets the organisation to one voice, and the supplier conversation that finally uses it.
Procurement & Supplier Negotiation · Read
When Your BATNA Is Not Having One
The most useful thing BATNA analysis can do in a sole-source situation is tell you the truth about your position. That truth is often uncomfortable — and it is more useful than pretending an alternative exists.
The Open-Minded Buyer
The curiosity that questions assumptions is what finds the value other buyers walk past. It is also a posture with real failure modes, and knowing where open-mindedness tips into lost commercial edge is part of using it well.
Deliberate Practice, and Why Experience Alone Does Not Make a Better Negotiator
Fifteen years in the role does not automatically make a buyer fifteen years better. Negotiation improves under specific conditions that ordinary working experience almost never provides, and understanding those conditions changes what a procurement leader should invest in.
Where Principled Negotiation Stops Working
Fisher and Ury's framework transformed how people think about negotiation. It also assumes conditions — mutual interest in agreement, separable people and problem, discoverable objective criteria — that adversarial procurement situations often do not have.
Train the moment, not the theory.
Voice2Evolve puts you in the scenario repeatedly until your reaction under pressure is no longer panic.