SRM is probably the most misunderstood Procurement initiative. Everyone agrees on its strategic relevance. Everyone recognizes that a well-managed supplier relationship creates value. Yet studies converge: more than half of formal programs launched over the past ten years have not achieved their initial objectives. Why?
Field experience reveals five recurring pitfalls. None is insurmountable, but none resolves itself.
01.Wanting to manage too many suppliers at the same level
The most common mistake: applying the same SRM model to 200 suppliers. Predictable consequence: exhaustion of Procurement teams, frustration of non-strategic suppliers saturated with unnecessary processes, and progressive abandonment of the program.
The Pareto rule applies brutally to Procurement: 15% to 20% of your panel represents 70 to 80% of your strategic value. These are the suppliers where governance investment is justified. For the others, minimalist monitoring is enough. Without this rigorous upfront segmentation, an SRM program collapses under its own weight within 18 months.
02.Confusing SRM with performance management
Many organizations reduce their SRM to a supplier evaluation system: scoring grids, scores, rankings. This is necessary, but largely insufficient. A strategic supplier expects a dialogue, not just a report card.
True SRM integrates performance, but adds co-construction (collaborative improvement plans), innovation (active solicitation of suppliers on your challenges) and governance (interaction rituals at multiple hierarchical levels). If your program is just an Excel file filled in once a year, you don't have SRM.
03.Underestimating the internal cultural dimension
An SRM program requires posture changes from your buyers. The traditional reflex consists of keeping the supplier under constant pressure. SRM demands the opposite: recognizing performance, sharing perspectives, investing time in the relationship. For many buyers trained in the "maximum pressure" school, this is a culture change, not a procedure change.
Without team support (training, coaching, adjustment of individual objectives), the program remains theoretical. Buyers continue to behave as before, and SRM crumbles.
04.Neglecting alignment with business units
Your buyers are not the only contacts for suppliers. User business units (production, R&D, IT, marketing) also have daily interactions, sometimes denser than those of Procurement. If your SRM ignores this reality, you get an official program managed by Procurement... and a parallel unmanaged relationship between suppliers and business units, sometimes contradictory.
An effective SRM systematically includes business units in governance, particularly for strategic suppliers. Tripartite Procurement-Business-Supplier committees, shared indicators, aligned viewpoints. Without this, the supplier receives contradictory signals and navigates blind.
05.Wanting to tool everything before structuring it
SRM platform vendors (SAP Ariba Supplier Lifecycle, Coupa SIM, Ivalua, etc.) offer powerful tools. But deploying a tool before clarifying your approach, your processes, your segmentation and your rituals amounts to industrializing emptiness. The IT project deploys, the tool works technically, and no one uses it. Classic case.
The winning sequence: 1) Define the SRM strategy, 2) Structure governance manually for 6 to 12 months, 3) Then identify which elements deserve specific tooling. Technology serves the approach, never the reverse.
The conditions for success
Successful SRM programs share a few common characteristics: a visible executive sponsor committed over time, rigorous segmentation, a limited number of truly managed suppliers (rarely more than 20-30), manual governance before tooling, and real investment in buyer training.
These conditions are nothing extraordinary. They simply assume not skipping steps and accepting that SRM is a 24-36 month program before producing its full effects. It is this temporal discipline that distinguishes programs that transform from programs that fade away.