Every procurement transformation I've been part of had a technology story. Most of them also had a people story. The technology story was the one in the project updates. The people story was the one that determined whether it actually worked.
Stakeholder management is the part of transformation that everyone agrees matters and almost nobody treats as a discipline. It gets a workshop. It gets a communications plan. It gets a slide in the governance deck. And then it gets deprioritised when the go-live pressure builds.
That's where transformations quietly fail.
Why transformation fails without stakeholders
Procurement touches every part of a business — finance, operations, legal, IT, and every supplier relationship the organisation depends on. A transformation that changes how procurement works changes how all of those functions interact with it. That's a lot of people with a lot of reasons to resist, disengage, or simply ignore what's being asked of them.
The common failure patterns I see aren't dramatic. They're quiet. Stakeholders who attend the workshops and say the right things — and then carry on as before. Business units that find workarounds because nobody made the new way easier than the old way. Senior sponsors who signed off on the business case and then moved on to the next priority, leaving the programme without air cover when it needed it most.
None of these are technology problems. They're relationship problems. And no platform fixes a relationship problem.
What stakeholder management actually means
It's not sending updates. It's not hosting workshops. Done properly, it's something closer to diplomacy — understanding what people need, what they fear, and what would have to be true for them to genuinely support the change rather than just tolerate it.
That starts with mapping. Not the standard RACI — something more honest. Who actually has influence here, regardless of their title? Who has been burned by a previous transformation and is waiting for this one to fail? Who stands to lose something real if this succeeds — a team, a process they own, a way of working they've built over years?
Once you know that, you can have real conversations. Not briefings. Conversations. What does this person actually need from this transformation? What would make them a champion rather than a skeptic? What are they not saying in the room that they're saying in the corridor?
The answers to those questions are where the real programme design lives.
The moment that changed how I think about this
In one global procurement platform rollout I was part of, early resistance from a key business unit was threatening the whole adoption timeline. The standard response would have been more training, more communications, more escalation.
Instead, we stopped. We went back to that business unit and asked a different question — not "why aren't you adopting?" but "what would have to be true about this system for it to actually work for you?"
The answers were specific and fixable. Workflows that didn't match how they actually operated. Approval thresholds that were wrong for their spend profile. A supplier onboarding process that created friction with relationships they'd spent years building.
We fixed those things. And then we asked them to help us fix them — to co-design the workflows, to define the thresholds, to shape the supplier onboarding approach for their category. They went from the programme's biggest obstacle to its most vocal advocates. Not because we persuaded them. Because we listened.
In another programme — a service redesign that had been stalling for months — the turning point came when we stopped presenting to stakeholders and started blueprinting with them. Their feedback wasn't a risk to manage. It was the design input we'd been missing.
What procurement leaders have to do differently
The skills that make someone a strong category manager or a capable P2P lead are not the same skills that make someone an effective transformation stakeholder manager. That gap is real and it doesn't close by itself.
The capability that matters most is what I'd call executive translation — the ability to take what procurement is trying to achieve and frame it in terms that land for a CFO, a COO, a general counsel, or a business unit director who has seventeen other things on their mind. Not dumbing it down. Connecting it to what they actually care about.
Beyond that, there's the coaching dimension. A transformation asks people to change how they work, often significantly. That's uncomfortable. Procurement leaders who can sit with that discomfort — who can help their teams and their stakeholders navigate it without either dismissing it or being derailed by it — are the ones whose programmes actually land.
And then there's the long game. Stakeholder management isn't a phase you complete at blueprinting and then move on from. The relationships that matter in go-live month are the ones you invested in twelve months earlier. The sponsor who goes to bat for you when something goes wrong is the one you kept genuinely informed — not with RAG updates, but with honest conversations — throughout.
The mindset shift that matters
The organisations that get procurement transformation right treat stakeholders as co-pilots, not passengers. That's not a platitude. It's a specific design choice — about who gets in the room, at what stage, with what authority to actually influence what gets built.
When that choice is made well, something interesting happens. The resistance doesn't disappear — resistance is information, and you need it. But it surfaces earlier, when you can still do something about it. The workarounds get designed out rather than worked around. The adoption curve looks different because the people who were supposed to change their behaviour actually helped design the thing they're being asked to change to.
Transformation is not a solo act. The technology is the easy part. The humans are the work.
