Why Procurement Digital Transformations Fail (and the Delete-First Method)

I’m kinda joking. This doesn’t keep me up. Only my kids tend to do that nowadays. But this was a very real problem that I had faced during my practitioner days.

Procurement transformations often struggle for a simpler reason than the technology choice: teams digitise processes before deciding which steps still deserve to exist.

I repeatedly see well-intentioned teams move long approval chains, duplicated forms and unclear ownership into a new platform, then expect the platform to resolve the underlying design problem.

Technology can help, but it cannot decide which parts of a process should exist.

If the underlying process is unclear, digitisation can make the confusion faster and harder to unwind.

Here's the uncomfortable truth: the problem isn't the technology. It's our thinking.

We're so busy digitising "how we've always done it" that we never stop to ask if those processes make sense in the first place.

AI adds another layer of capability, but it does not remove the need for process judgement. When intelligence is placed on top of unclear rules, poor data or excessive hand-offs, the team can automate the wrong work more quickly.

Teams often scatter resources across every possible improvement opportunity. They try to digitise all processes, optimise every category and implement broad solutions at the same time instead of agreeing where focused change matters most.

Spend analytics and other tools do not create adoption or action by themselves. The practical test is whether the information changes a decision, clarifies an owner or improves a workflow.

The result of an unfocused programme can be a diluted budget, slow adoption and months spent perfecting low-impact features while the most important processes remain untouched.

Let me introduce you to the Delete-First Method—the five steps I now consistently follow whenever I'm leading or advising a procurement transformation, or building out any new business process.

This isn't consulting theory. It's a field-tested, scar-tissue-earned approach that works because it forces you to think before you digitise.

Ask "Why?" till it hurts. When you hear "that's just how it's always been done," you're on the right track. Don't stop until every approval, form, and step has a clear reason for existence—tied to value or compliance.

I tell my kids to do this.

It’s one of the greatest Mental Models that we can access.

Deeply prioritise what matters and lose everything else.

Most processes accumulate steps like barnacles. If a step doesn't directly drive your outcomes, cut it.

The simple truth here is that you can always add something back in. Nothing is permanent.

Now clarify.

Can someone unconnected to your organisation walk in, read the process, and execute it without confusion? If not, it's still too complex.

Simplicity isn't laziness.

It's what reveals where real value lives.

Speed is your friend, but only once you've stripped away the unnecessary.

If you accelerate a flawed process, you amplify mistakes. Tackle bottlenecks, improve feedback loops, and set ambitious SLAs after simplifying.

Now, bring in automation and tech. If you're automating clear, logical, and valuable steps, you're on the right track. If not, you're just making bad faster and more expensive.

Remember: Technology amplifies clarity, not chaos.

Let's get honest: this approach feels risky, even existential, to most organisations. Why?

Compliance is non-negotiable. Separate legal, regulatory and policy controls from habits that have accumulated without a clear owner or purpose. Preserve required controls and challenge the rest.

Culture changes when people can see a safer and simpler way to work. Start with one visible process, involve the people who operate it and demonstrate the result before widening the programme.

Consultants are only helpful if you're willing to question your processes first. They can't drive the hard internal conversations for you.

Of course! But don't waste skilled minds on process noise. Free them to tackle the ambiguous, once you've cleared the easy stuff with your delete-first approach.

Here is a practical route from a broad transformation ambition to a process that is ready to digitise:

Share your worst digitised-bureaucracy story in the comments. The useful question is not whether a transformation matched an industry benchmark; it is whether the process became clearer, faster, safer and easier to operate.

Thank you for supporting WOP and its practical procurement frameworks.

This article does not assert an industry-wide procurement transformation failure rate. Earlier unsourced benchmark figures were removed because the original studies were not linked with enough context to verify the claims.

The Delete-First Method is a WOP practitioner framework based on Daniel Barnes's experience. Test it against your organisation's controls, risk appetite and measurable outcomes.

It is a five-step WOP framework: question every requirement, delete unnecessary work, simplify what remains, improve cycle time and automate only after the process is clear.

Not always. Technology, process design, data, ownership, controls, integration and adoption interact. This guide focuses on the process-design failure mode because teams can address it before implementation.

No. Required legal, regulatory and policy controls must remain. The work is to distinguish necessary controls from duplicated steps, unclear hand-offs and habits without a current purpose.

Run a small pilot before automation. Observe errors, exceptions, user effort, cycle time and control performance, then adjust the process before scaling it.