Ask a CIO whether their organization manages its IT vendors and the answer is yes. There is a vendor management office, a contract repository, a quarterly business review, a scorecard with green cells. Ask the same CIO whether the organization is getting the value it pays that vendor for, and the answer is a pause.
That pause is the difference between vendor management and Vendor Value Management. This article sets out what each one is, where the first one stops, and why the second one exists.
What vendor management is
Vendor management is the set of activities an organization performs to run its relationships with suppliers: selecting them, contracting with them, onboarding them, tracking their performance against SLAs, managing risk and compliance, handling escalations, and administering renewals. It is mature, well documented, and supported by an entire industry of tools and certifications.
Its unit of work is the vendor's outputs: deliverables, KPIs and SLAs, tickets, contracts, invoices, risk ratings. Every artefact it produces, the scorecard, the risk rating, the contract summary, the relationship map, describes a part of the relationship and how that part is performing.
That is exactly what it was designed to do, and it does it well. The problem is what it was never designed to do.
Where vendor management stops
Vendor management answers the question is the vendor doing what we agreed? It does not answer the question was what we agreed worth it, and is it still?
Those sound similar. They are not. A vendor can meet every SLA, pass every audit, keep every commitment in the contract, and the organization can still be losing value on the relationship every month. Anyone who has run outsourced IT for long enough has seen the pattern: the dashboard is green, the invoices are paid, and the business quietly stops relying on the service because it no longer does what they need. In Vendor Value Management this is called the watermelon effect, green on the outside, red inside.
The reason it happens is structural, not a matter of effort. Several functions each govern a slice of the vendor relationship from their own angle. Procurement governs price. Legal governs terms. Service management governs tickets and SLAs. Finance governs the invoice. Risk governs exposure. Each one optimizes its own metric, and each one can report success while the relationship as a whole is failing the business, because no one of them is accountable for the whole.
Vendor management, as practiced, is the coordination layer across those functions. It makes sure each slice is being handled. It does not own the question that sits above all of them.
What Vendor Value Management is
Vendor Value Management (VVM) is a management discipline for the continuous governance and management of business value from vendor relationships. It asks one governing question of every relationship, at every stage: is this relationship still justified?
The shortest way to state the difference is this: vendors are governed not managed; value is governed and managed.
Vendor management governs vendors. VVM governs and manages value. That means VVM has to do two things vendor management never had to.
First, it has to define value in a way that can actually be governed. In VVM, value is the net, intentional benefit expected from a vendor relationship, relative to its cost, its risk, and the viable alternatives, and it is assessed continuously rather than at renewal. Value has four properties: it is intentional (someone stated it), relative (measured against alternatives, not in isolation), contextual (what counted as value at signing may not count as value now), and temporal (it decays, and it has to be re-earned).
Second, it has to give that value a named owner. VVM introduces two roles. The Value Owner is a business role, accountable for the continue, restructure, or exit decision on the relationship. The Value Manager operates the framework and keeps the evidence decision-ready. Without a Value Owner, the discipline is inoperable, because there is nobody whose job it is to answer the governing question and act on the answer.
Contracted value, realized value, and the leakage in between
The concept that makes VVM measurable is the gap between two numbers.
Contracted value is what the relationship was supposed to deliver: the outcomes, the service levels, the capacity, the options it was meant to create, at the price and risk agreed.
Realized value is what the organization actually receives.
The difference is value leakage, and the central claim of VVM is that leakage accumulates even when every vendor management metric is green. It is not detected by the scorecard because the scorecard was built to measure the vendor, not the value.
VVM classifies leakage into three types, each with its own diagnostic indicators:
- Strategic leakage (intent): the value the relationship was meant to produce was never made explicit, has no owner, or has drifted; the relationship has become transactional and nobody is asking whether it still fits.
- Structural leakage (design): the commercial model bakes in overpayment; consumption is unchecked; licences and capacity overrun; there is no holistic view of performance across contracts.
- Execution leakage (behaviour): scope creep, unclaimed service credits, tickets closed before they are resolved, clock-stopping on-hold abuse, change requests that do not match the contract.
Vendor management, when it is done well, catches some execution leakage. It rarely sees structural leakage, because that is designed in. It almost never sees strategic leakage, because nobody in the vendor management process is asking the strategic question.
Governance that decides, not governance that observes
The second thing VVM changes is what governance is for.
Most vendor governance produces reports. A steering committee meets, reviews the scorecard, notes the risks, and adjourns. The relationship continues by default. Renewal arrives and is processed as an administrative event, often by procurement, often on the basis that switching would be disruptive and the vendor is "fine."
VVM treats that as governance theater. Its manifesto rests on four axioms:
- Governance exists to decide, not observe. The decision is the unit of governance. A forum that produces reports instead of decisions is not governing.
- Renewal is a governance decision, not administration. Every renewal is a fresh continue, restructure, or exit decision, made on evidence.
- Assumed value cannot be governed. If value has not been made explicit, baselined, and measured, there is nothing to govern, only spend to approve.
- A relationship that cannot be safely exited is not properly governed. Exit-readiness is the proof that the organization, not the vendor, holds the decision.
Read those against a typical vendor management process and the gap is obvious. Vendor management is very good at observing. It is not built to decide, because the decision was never its job.
Side by side
| Vendor management | Vendor Value Management | |
|---|---|---|
| What it works on | The parts of the relationship: deliverables, KPIs and SLAs, tickets, contracts, invoices, risks | The relationship as a whole: the value it delivers relative to its cost, risk and alternatives |
| Governing question | Is the vendor doing what we agreed? | Is this relationship still justified? |
| Primary evidence | SLA attainment, compliance, risk rating | Realized value vs contracted value; leakage by type |
| Owner | VMO / procurement / service management | A named business Value Owner, supported by a Value Manager |
| Renewal | An administrative event | A governance decision: continue, restructure, or exit |
| What "green" means | The vendor met its metrics | The relationship is still earning its cost and risk |
| Failure mode | Governance theater; the watermelon effect | Requires a real owner and real evidence, or it does not run |
Why this matters now
Organizations spend hundreds of billions a year on outsourced IT services, and the audit record of large programmes, ArriveCAN, Phoenix Pay, the NHS National Programme for IT, Healthcare.gov, tells the same story across different jurisdictions and decades: the governance that existed was never designed to own the value question, so nobody did. Those were not failures of effort. Every one of them had vendor management. What they lacked was a discipline accountable for whether the vendor relationships were still worth having.
VVM does not replace vendor management. Procurement still needs to procure, legal still needs to contract, service management still needs to run the service. VVM sits above them and does the one thing none of them do: it makes vendor value explicit, gives it an owner, measures the leakage continuously, and connects the result to the decisions that determine whether outsourcing actually works.
If your vendor dashboard is green and you still have that pause when someone asks whether the money is well spent, that is not a vendor management problem. That is the problem Vendor Value Management was written to solve. #VendorValueManagement #VendorManagement
Haitham Merah is the author of Vendor Value Management: Governing Value Across the Vendor Lifecycle and the founder of ValuFy, the Vendor Value Management platform. He has spent over 25 years in IT service delivery and vendor governance at Hoffmann-La Roche, Deloitte, IBM/Kyndryl, BP, Vodafone and the Government of Ontario.