Elevating SRM: From Framework to Competence

The first shift: from compliance to mutual value

The most common misconception holding organizations back is treating SRM as a reactive, compliance-driven activity -something that monitors performance, enforces terms and resolves issues after the fact. Leading organizations have made a deliberate shift in the opposite direction. As WorldCC’s SRM Focus podcast puts it: "SRM should be proactive and a strategic discipline aimed at creating mutual value" [1]. That sounds obvious, but the structural implication is significant. It means the SRM function is not measured on how well it polices suppliers, but rather it is measured on whether it is fundamentally changing business outcomes.

You might consider asking a simple diagnostic question: does your SRM team spend more time looking backward at performance data, or forward at shared goals? Or another way of looking at this is: does SRM focus primarily on what your organization wants, or more on understanding what the supplier is capable of giving and how the way your organization behaves is impacting that? The answer tells you almost everything about whether SRM is embedded or merely administered, whether its view of the world is inside looking out, or outside looking in.

The business case for making this proactive shift is well established externally too. McKinsey research across more than 100 large organizations in multiple sectors found that companies which regularly collaborated with suppliers demonstrated higher growth, lower operating costs, and greater profitability than industry peers, with those possessing advanced supplier-collaboration capabilities outperforming peers by approximately two times on growth metrics. The value at stake is significant. The barrier is not knowledge; it is the willingness to reorient the function. [2]

The second shift: integration across the relationship lifecycle

One of the most consistent findings from WorldCC's SRM research is that both SRM and contract management are "often not really thought of in a holistic lifecycle way", and that contract managers and relationship managers "often get excluded from key components of the process, which massively constrains what they're able to contribute" [3]. This is a structural problem. Legacy systems were designed around siloed organizations, and the people inside them behave accordingly.

Leading organizations break this pattern by embedding SRM early - often before procurement involvement, certainly before the contract is signed - with upfront conversations that examine the technical solution, the commercial model, and the form of relationship needed to deliver the outcome, all at the same time. The principle is simple: "Collaboration doesn't start when a contract is signed, it starts much earlier and continues long after" [4]. That is not a cultural aspiration. It is an operating model choice.

The World Economic Forum's work on future-proofing global value chains has reinforced this point structurally: value creation in modern supply relationships increasingly happens across organizational boundaries, not within them. The implication for SRM is clear. A function confined to its own organizational perimeter is not managing the relationship, it is acting purely with self-interest [5].

The third shift: measuring what actually matters

The measurement question is where most SRM programs quietly fail to reach their potential. Organizations default to KPIs that measure supplier performance - delivery, quality, cost - and then wonder why the relationship feels transactional. The Enhancing Collaboration through Effective Relationship Management report found that almost half of surveyed organizations do not actively gather structured supplier input at all [4]. Collaboration cannot be built on a singular, unilateral view.

What distinguishes the more advanced programs is a move toward OKRs - objectives and key results - alongside traditional KPIs. OKRs drive "forward-looking and collaborative ambition and behavior" and ensure "good governance standards that support shared ownership and adaptability" [3]. Some leading organizations go further, using a "commitment realization rate" - a single metric that consolidates contractual and relational commitments (joint plans, governance meetings, innovation workshops, executive reviews) and measures the proportion fulfilled [3].

The signal this sends is powerful: it says that shared commitments matter, not just supplier deliverables.

The fourth shift: treating the supply base as a portfolio, not a list

There is a structural discipline that leading organizations apply which most do not: deliberate supply ecosystem design. Rather than managing thousands of suppliers with limited contact, they structure their supply base intentionally – for example, one prime, a challenger, and one or two niche suppliers in each critical category [5]. The logic is straightforward. Having 10,000 suppliers dilutes negotiating power, relationship investment, and economic value simultaneously. And the endless competitive bidding that this implies is a sure-fire way to destroy supplier loyalty and commitment. Segmenting on risk, not just spend, and then concentrating relationship investment on the top 10 to 20 strategic suppliers is where the returns actually live [1].

The Hackett Group's benchmarking data lends empirical weight to this. They discovered that top-performing procurement organizations maintain 2.3 times fewer strategic suppliers than their lower-performing peers, and supplier consolidation in the top quartile has been associated with meaningful reductions in indirect spend costs. During the pandemic, the Hackett Group's research found that organizations with stronger, more concentrated supplier relationships secured significantly better access to allocated supply than those with a fragmented supply base. This resulted in a performance difference that showed up directly in business continuity. Fewer, deeper relationships proved to be a risk mitigation strategy. [6]

The Enhancing Collaboration through Effective Relationship Management report found that 90% of respondents believe formal SRM can help overcome current impasses in supplier relationships [6]. Yet 47% of customers say they do not engage in SRM at all [4]. That gap, between belief and practice, is the real challenge. It is not so much a knowledge problem as a prioritization and governance problem.

The fifth shift: making the contract a foundation, not a ceiling

A large group of CPOs recently confessed to a sentiment they had in common: "contracts are a necessary evil." It mirrors another frequent view that "it's the relationship that matters."

These attitudes are understandable. But they are also a form of learned helplessness, a response to contracts that have consistently failed to serve the people who need to use them. The answer is not to dismiss the contract. It is to fix it, to make it ‘fit for purpose’.

Nobel laureate Oliver Hart's work on incomplete contract theory, for which he was awarded the 2016 Nobel Prize in Economics, established the point that no contract can anticipate everything. [7] As Hart has argued, the longer and more complex the relationship, the more situations will arise that the contract is simply silent on. This is not a failure of drafting, it’s a structural property of contracts in conditions of uncertainty. Hart's conclusion was not that contracts are therefore unimportant, but that how parties design for incompleteness - the governance mechanisms, the relational commitments, the flexibility built into the agreement - matters enormously for what actually happens when the unexpected occurs.

That insight directly challenges the two most common reasons contracts are dismissed. The first is rigidity: contracts written as though the future is knowable, with fixed terms and few adaptive mechanisms, become obstacles the moment circumstances change. The second is inaccessibility: contracts drafted in typical legal language and confusing structural design are functionally useless to the commercial and operational teams who must live with them every day. Neither of these is a required property of contracts: they are design failures. It is a choice when we make contracts rigid, adversarial and of little or no use to the wider business - and it is therefore a choice we can reverse.

The best performing organisations treat the contract as the instrument that enables trust, not the instrument that substitutes for it. As one practitioner put it in the Trust and Transparency webinar, when discussing the importance of data exchange: "If it has no teeth, if it's not in the contract, I can't ask for the data" [8]. The contract must establish the basis for fundamental rights and obligations such as transparency, joint goal-sharing, and performance accountability, and it must do so in language that the people responsible for delivering on those commitments can actually read and act on.

The organizations that get this right treat SRM and contracting as "deeply connected" rather than two separate activities [3]. The contract creates the architecture; the relationship fills it with life. Neither works without the other.