<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=11114857&amp;fmt=gif">
Skip to the main content.

2 min read

The Transformation Playbook Procurement Needs to Retire

The Transformation Playbook Procurement Needs to Retire

For much of my career, procurement transformation has followed a familiar pattern. Procurement identifies the limitations of our existing systems, builds a business case for something better, and embarks on a multi-year implementation that requires significant investment before we see meaningful results.

I've been involved in enough of these projects to understand why procurement leaders are reluctant to start another one. The technology may have changed with AI, but the organizational fatigue associated with transformation hasn’t moved an inch.

That was on my mind during a recent AOP Live discussion with Patrick Reymann, Research Director at IDC; Rick Raker, Director of Procurement at Pfizer; and Matt Kapadia, Vice President of Enterprise Solutions at ORO Labs.

What struck me about our conversation was the need to challenge long-held assumptions about transformation. We have spent years treating our existing technology investments as constraints that determine what procurement can do next. Increasingly, I think we're discovering that those constraints are much less permanent than we believed.

When Technology Dictates Process

One question I raised during the discussion was whether years of accumulating so-called ‘technical debt’ have also created process debt.

Think about how many procurement processes exist today because of the limitations of a system implemented a decade ago (or more). We have designed workflows around software requirements, trained employees to navigate complicated interfaces, and measured improvements by how many clicks we could eliminate.

Rick shared an observation from a newer colleague at Pfizer who questioned why reducing clicks was even a meaningful metric. Her expectation was that she should be able to communicate what she needed and have the technology handle the work. In other words, why click at all?

We've become so accustomed to optimizing the procuretech user experience that we haven't questioned whether people should need to interact with those systems in the first place. Intake and orchestration technology opens up a different possibility. The underlying systems can continue doing the work they were designed to do, while the experience of accessing them changes considerably.

For organizations with substantial investments in existing infrastructure, that creates an opportunity to modernize without starting over.

Progress Creates Its Own Momentum (and Buy-In)

Rick described automating a 17-step requisition review process across 78 markets and covering approximately 250,000 annual transactions. The implementation took six weeks. That timeline would have been difficult to imagine under the traditional transformation model, but there was still more to come.

That success prompted business stakeholders to identify additional processes that would benefit from the same approach. Opportunities emerged that procurement hadn't recognized when the project began.

Procurement leaders often feel the need for a comprehensive roadmap before they can justify an investment. At the same time, demonstrating tangible value through a focused implementation can create the organizational confidence needed to pursue more ambitious improvements. It also allows us to confirm what the business needs rather than making assumptions.

AI Raises the Stakes

Patrick made an important observation about AI's relationship with existing technology architecture. AI exposes weaknesses in data quality and process design that organizations have historically managed through human intervention. As we introduce more autonomous capabilities, those weaknesses become harder to ignore.

I also found our guests’ insights around AI governance particularly relevant. There is enormous pressure to introduce agents into procurement workflows, but we need to remain disciplined about where they create value and how they operate within appropriate controls. Otherwise, we risk recreating the very complexity we're trying to escape.

A New Kind of Transformation

I left the discussion thinking about how fundamentally procurement’s definition of transformation is changing.

We no longer have to accept that meaningful progress requires years of preparation followed by a disruptive implementation. We can identify a problem worth solving, demonstrate value relatively quickly, and use what we learn to inform the next investment.

For CPOs who have spent years navigating successive transformation programs, that's an encouraging prospect. Now, we just have to recognize that the playbook we've relied on for so long may be the very thing holding us back.

 

Links: