Procurement transformation
Procurement transformation: where should businesses start?
Most procurement transformations stall because they start with the solution. A practical sequence for deciding what to change first — and what to leave alone.
Procurement transformation has a reputation for being expensive, slow and disruptive. Sometimes that reputation is deserved. More often, the difficulty comes from starting in the wrong place — usually with a solution, such as a new system, a new structure or a new policy, before anyone has agreed what problem it is meant to solve.
This article sets out a practical sequence for deciding where to start, and how to build momentum without trying to change everything at once.
Start with what the business needs from procurement
Before looking at procurement itself, it helps to ask what the rest of the organisation needs from it. The answer differs significantly between businesses:
- A mining operation may prioritise continuity of supply for critical spares and consumables, with cost a close second.
- A construction business may care most about getting packages awarded on time and protecting margin through the life of a project.
- A private equity-backed business may need measurable cost improvement within a defined period, and clean reporting to support it.
- A growing industrial business may simply need control — knowing who is committing spend, against what agreements, and with what approval.
These priorities shape everything that follows. A transformation designed around cost reduction will look quite different from one designed around supply continuity or control.
Establish an honest picture of today
The second step is an honest assessment of the current state. That typically covers four areas:
- Spend. What the organisation buys, from whom, how much is under contract, and how fragmented the supply base is.
- Process. How a need becomes a purchase order, a receipt, an invoice and a payment — and where it breaks down or is worked around.
- People and structure. Who does procurement work, with what skills, and where decision rights actually sit.
- Systems and data. Whether the systems support the process, and whether the data in them can be trusted.
The goal is not a lengthy report. It is a shared, evidence-based view that leadership, operations, finance and procurement all recognise. Without that agreement, every later decision becomes a debate about the starting point.
Separate quick improvements from structural change
Assessment usually surfaces two types of opportunity.
Quick improvements can be delivered within existing structures: renegotiating an expiring contract, consolidating suppliers in a fragmented category, tightening approval limits, or clarifying a confusing process step. They deliver early value and build credibility.
Structural changes take longer: redesigning the operating model, implementing or reconfiguring a system, building category management capability, or changing how procurement engages with the business. They deliver lasting value but need sponsorship, planning and patience.
A good transformation plan runs both in parallel. Early improvements create the confidence and, often, the savings that make the structural work easier to support.
The most useful early question is not "what should procurement look like?" but "what is getting in the way of the business right now?"
Sequence the structural work carefully
When it comes to structural change, order matters. A common mistake is implementing a new system before the processes and roles it is meant to support are clear. The system then either encodes the old problems or forces a design nobody has agreed to.
A more reliable sequence is usually:
- Agree the strategy — what procurement must deliver, and how success will be measured.
- Design the operating model — roles, structure, decision rights and how procurement engages with the business.
- Define processes and controls that are proportionate to the organisation's size and risk.
- Configure or implement systems to support those processes.
- Build capability so people can work effectively in the new model.
There are exceptions — sometimes a system change is already committed and the work must be organised around it — but the principle holds: design the way of working before automating it.
Make ownership explicit
Transformations falter when ownership is vague. Each initiative needs a named owner in the business, an agreed measure of success and a regular point at which progress is reviewed. Where procurement depends on other functions — finance for payment terms, operations for specifications, IT for systems — those dependencies should be visible and agreed, not assumed.
Know when to leave things alone
Not everything needs to change. Parts of the current approach may already work well, and disrupting them carries risk. Part of a good assessment is identifying what to protect: the supplier relationship that is genuinely strong, the site team that runs an efficient local process, the contract that is already competitive.
A practical starting checklist
If you are considering a procurement transformation, these questions are a useful place to begin:
- What does the business most need from procurement over the next two to three years?
- Do leadership, operations and finance share the same view of the current problems?
- Which improvements could be delivered in the next three to six months without structural change?
- Are any system changes already committed, and how will the work align with them?
- Who will own each initiative, and how will progress be measured?
Answering these honestly will usually make the right starting point clear.
Valuewright helps organisations assess their procurement function and design practical, staged transformation programs. Learn more about procurement transformation or our approach.