Most SRM programs fail before they start. Not because of poor design, insufficient budget, or lack of executive commitment — though those contribute. They fail because of a category error at the beginning: the belief that ambition and scope are the same thing.
Leaders approach supplier relationship management the way they approach most enterprise initiatives. They survey the landscape, identify the full set of things that should be done, design a program that addresses all of them, build a business case for the investment, and then wait for approval and resources before beginning. By the time the program launches, the organization is already exhausted, the sponsors have shifted attention, and the first review cycle reveals that the scope was more theoretical than operational.
I have watched this pattern repeat across organizations that had the right intentions, the right frameworks, and the wrong starting posture. The most successful SRM programs I have seen began with focused pilots that demonstrated value before scaling. The ones that failed almost always attempted enterprise-wide transformation from day one.
The Psychology Behind the Wrong Approach
The instinct toward comprehensive design is not irrational. Procurement leaders are often asked to justify SRM investment against competing priorities, and a narrow initial program invites the obvious question: why are we spending this much for something so limited? The instinct is to preempt that criticism by showing scope.
But this logic mistakes visibility for credibility. A program that covers twenty suppliers with three meaningful practices creates more organizational trust in twelve months than a program that covers two hundred suppliers with five practices that no one enforces. The first one changes how people think about supplier relationships. The second one creates compliance work without changing outcomes.
Starting small is also threatening to a certain kind of organizational culture. There is an implicit assumption in many enterprises that anything worth doing is worth doing comprehensively. Focused pilots feel like hedging. In reality, they are the opposite: a leader confident enough in the approach to put a small version of it in front of real organizational scrutiny.
What Minimum Viable SRM Actually Means
The Minimum Viable SRM concept is simple: the smallest set of disciplined practices that can create focus, accountability, and business impact with the resources currently available. It is not a compromise. It is not a placeholder until the real program launches. It is a deliberate strategy to demonstrate value, build organizational capability, and earn the right to scale.
A Minimum Viable SRM program typically includes five elements, each at its most focused form.
Segmentation. Simple tiering based on spend and criticality. Three to five strategic suppliers. Ten to fifteen critical suppliers. The discipline is in the criteria, not the count.
Governance. Quarterly business reviews for the top five to ten suppliers. Standing agenda. Shared preparation. Someone who owns the relationship on both sides.
Performance. A five-metric scorecard tracking the essentials: delivery, quality, responsiveness, cost competitiveness, and collaboration. Five forces you to choose what actually matters.
Risk. Basic monitoring for your most critical suppliers. Annual financial health review. News monitoring. Documented contingency thinking for the two or three suppliers whose failure would hurt the business most.
Technology. Spreadsheets until processes are proven. Not because spreadsheets are ideal, but because technology amplifies existing capability rather than creating it. Know what you are doing before you automate it.
This is not a reduced ambition. It is a refusal to let aspiration outrun capacity.
The 30-60-90 Day Launch Sequence
For an organization starting from zero, the first ninety days are about establishing the foundation on which everything else can be built. The goal is not to have a complete program. The goal is to have a functioning one.
In the first thirty days, the work is entirely on segmentation and internal alignment. Identify your top twenty suppliers by spend and criticality. Apply simple tiering criteria. Assign internal ownership. In most organizations, asking who owns the relationship with a given strategic supplier produces either a confused answer or three competing answers. Clarifying ownership is the foundation of everything else.
Days thirty-one through sixty are structural. You conduct the first round of quarterly business reviews with your top five to ten suppliers. You complete a basic risk assessment across your strategic tier. You begin building the scorecards that will make those reviews substantive.
Days sixty-one through ninety are iterative. You complete the first full review cycle, assess what worked and what did not, and adjust accordingly. The goal at ninety days is not a perfect program. It is a program that the organization can sustain — that does not depend on heroic individual effort, produces visible results, and has demonstrated enough value to justify the next phase of investment.
The Principle Beneath the Framework
The deeper argument here is about organizational learning. SRM programs that begin at full scale have nowhere to go when the first assumptions prove wrong — and the first assumptions almost always prove wrong. A program designed at minimum viable scale encounters these problems when they are still small. A program designed at enterprise scale encounters them after a year of investment and organizational commitment, when acknowledging the problems is politically costly.
The organizations that build durable SRM capability — where supplier relationships are genuinely managed, not just nominally tracked — almost universally got there through iteration. They learned on a small number of suppliers before applying those lessons to a larger population. They built processes before they automated them. They demonstrated value before they claimed it.
That discipline is the only path that consistently arrives at the destination.
Jason Cipriano is the founder of VIDONAS and the author of Procurement 4.1 and SRM 2.0.