A procurement leader comes back from a three-day leadership programme with a new vocabulary, a better model for stakeholder influence, and the slightly evangelical energy people have after good training.

For about a week, it shows.

They ask different questions. They push earlier. They try to move the conversation from savings to value. Then the old machinery starts up again. The urgent sourcing event. The stakeholder who only wants a contract signed. The CFO asking for the number.

By Friday, the new behaviour is inconvenient, if not totally forgotten.

Most procurement leadership development fails not because programmes are poorly taught, but because they treat capability as an individual learning problem when procurement performance is a system problem. This article examines the five root causes of failure, from programmes with no value logic to operating models that reject the behaviours development is trying to create, and identifies what the exceptions consistently get right.

Leadership development is often judged by the things that are easiest to count and least likely to matter.

Attendance. Satisfaction. Completion.

Whether people liked the facilitator.

Whether the sandwiches were acceptable.

Whether the post-programme survey produced enough agreeable adjectives to justify running the same thing again next year.

The lesser asked question is whether anyone behaves differently six months later.

On this, the research is fairly consistent.

The workplace application of formal learning is stubbornly low.

Episodic programmes tend to have limited effects over time. Without structured application after the event, new concepts rarely survive contact with the operating environment.

Why? Because the organisation people return to often rewards precisely the behaviour the programme was trying to replace.

That is the point worth sitting with. The usual diagnosis of failed procurement leadership development is poor programme design. Sometimes that is true. But the other possibility is that the programme did work. It produced a different kind of leader.

The first article in this series looked at why the CPO role has been structurally rebuilt while most development pathways have not kept pace. This article looks at why the programmes that do exist so often fail to close the gap, and what the exceptions tend to get right.

We think that the failure rarely occurs in the classroom.

Most procurement leadership programmes look perfectly respectable while they are happening. The feedback is positive. The facilitator is engaging. The frameworks are useful. The cohort forms good connections. Everyone leaves with a notebook full of sensible intentions.

Then three months pass, and nothing changes.

This is not unique to procurement. These failure modes appear across industries and functions. But procurement sharpens them for a particular reason.

This creates a wider gap between learned behaviour and lived environment than exists in many other functions. It also makes the cost of failing to close that gap much higher.

Root causes of leadership development program fails  

1. No value logic

The first root cause is a programme with no clear answer to a basic question: what would be different in this function if this worked?

Not what would participants learn. That is the easy question.

What would change?

Would the CPO have a different quality of conversation with the CFO? Would procurement be involved earlier in demand decisions? Would more sole-source contracts be challenged before the specification had already hardened into concrete? Would category strategies show genuine market intelligence rather than a tidier version of last year’s sourcing plan?

If that question does not have a specific answer before the programme launches, the programme does not have a goal. It has a timetable.

This failure runs straight into measurement.

Most procurement leadership programmes measure satisfaction. That is not useless. It is a reasonable form of quality control. It tells you whether the room worked. It tells you whether people found the content credible. It tells you whether the facilitator should be invited back.

It does not tell you whether the function is now behaving differently.

Useful measurement for procurement leadership development looks more like this: earlier involvement in sourcing decisions, fewer late-stage procurement interventions, Finance-validated value capture rather than self-reported savings, and evidence that stakeholders are willing to involve procurement before specifications are fixed.

Those measures have to be designed deliberately. They do not emerge, like a small miracle, from a happy-sheet.

Procurement does make attribution harder than in some other functions. Savings move with markets. Avoided risk is invisible until the disruption that did not happen is compared with the one that did. Stakeholder influence is hard to reduce to a neat number.

But that is not an argument for retreating to satisfaction data.

It is an argument for designing the measurement properly before the programme begins.

2. Bad contextual design

The second root cause is content that does not translate into the work.

This is not an argument against leadership theory. Influence, sensemaking, decision quality, coaching, and change leadership are genuinely transferable capabilities.

The failure is leaving participants to do the translation themselves: to work out unaided what “influence without authority” means when the specific situation is persuading a divisional head to change a specification they have already socialised internally, or challenging a demand assumption in a project that has absorbed three months of planning.

Most people do not make that translation under workload and political pressure.

They return to existing behaviour because it fits the environment, and the programme gave them no traction on that environment.

Procurement adds a specific dimension: facilitation that cannot translate leadership theory into procurement work cannot coach the capability that actually matters.

A facilitator who does not understand federated category structures, sole-source supplier dynamics, or what it takes to build commercial credibility with a CFO who still sees procurement as a control function can run a leadership programme.

That is a different product from procurement leadership development.

3. No transfer system

A programme with no structured follow-up, no coaching, no peer accountability, and no designed application to live work delivers a predictable outcome: engagement for a few weeks and regression to baseline after that.

New concepts do not survive in an environment where the operating pressures, the performance metrics, and the manager’s expectations all point in the old direction.

Procurement is especially exposed to this.  

Category managers and business partners return to urgent sourcing events, contract renewals, and savings deadlines. Without protected time and explicit opportunities for application, reflective practice is the first thing to be cancelled.

The design logic of effective programmes reflects this.

The majority of leadership capability develops through structured experience and stretch assignments: doing difficult things, being accountable for real outcomes, making consequential decisions.

Coaching and peer learning play a significant supporting role.

Formal instruction matters, but as an amplifier of experience, not a substitute for it.

Most procurement leadership programmes invert this.

They are designed primarily around what can be delivered in a room, and they leave the application (the part where the development actually happens) to participants to manage themselves on return.

4. No executive sponsorship

The fourth root cause is sponsorship that is verbal rather than behavioural.

Visible endorsement is not enough.

In procurement, sponsorship means the CPO, CFO, and relevant business-unit leaders create the space for different procurement behaviours.

If senior leaders say they want strategic procurement but continue to measure the function primarily on savings and tactical responsiveness, participants draw the obvious conclusion about which signal is real.

Sponsorship means attending, setting expectations, providing air cover for different behaviour, and asking participants to apply their development to live enterprise priorities rather than treating it as a parallel track alongside the real work.

The direct manager matters at least as much as the senior sponsor.

The participant’s immediate manager controls workload, creates or blocks opportunities for application, and determines whether new behaviour is practised or crowded out.

A programme that develops participants while leaving their managers uninformed and unchanged has removed the conversion mechanism.

5. Operating model mismatch

The fifth root cause is the most specific to procurement, and maybe the most consistently overlooked.

A CPO who completes a well-designed leadership programme and returns to a function resourced for transactions, measured on savings alone, and structurally excluded from scoping conversations has nowhere to put the development.

The programme may have been excellent. The system rejected the output.

This is not a programme design failure in the conventional sense.

It is a failure to recognise that individual capability and organisational context are different problems that require different interventions. A procurement leader trained to operate strategically cannot sustain that behaviour in a function whose governance, operating model, stakeholder relationships, and performance metrics are all calibrated for a different purpose.

There is a subtler version of this failure. Some organisations reward fast turnaround, tactical responsiveness, and claims of savings.

They say they want strategic advisory procurement. They do not change what they measure or what they praise. The programme then works against the incentive architecture, and the incentive architecture is stronger.

This is why individual development and organisational capability building need to be sequenced together.

Developing the CPO while leaving the function’s operating model unchanged is a partial solution at best. The next article in this series examines where effective development actually starts, and why it begins with the organisation, not the curriculum.

What the exceptions have in common  

Programmes that work do not start by asking what to teach.

They start by asking what should be different in twelve months: in specific procurement conversations, in specific commercial outcomes, in specific decisions where procurement’s contribution was visible. Then they design backwards from that answer.

They are not better workshops. They are development systems: a baseline assessment, live work integration, executive sponsorship that changes expectations rather than just endorsing attendance, coaching, measurement designed before the programme launches, and an operating model that can absorb the behaviours the programme is trying to create.

The exceptional cases are not exceptional because of the content.

They are exceptional because the organisation treated procurement capability as infrastructure: something that required design, sustained investment, and organisational alignment, rather than a training budget line.

If you are evaluating a procurement leadership programme, or trying to make the case for one, the starting point is a clear picture of where your people actually are. The Academy of Procurement’s leadership programme is built around the design principles this article describes: structured baseline assessment, live procurement application, cohort and coaching support, and outcomes tied to what changes in the function.

If you want to understand how your team’s current capability maps against the demands of the role, the Skills Gap Analysis is a practical starting point.

To book a consultation – visit the bookings page here >

Get Procurement Insights That Matter

Join 10,000+ procurement professionals getting monthly expert cost-optimisation strategies and exclusive resources. Unsubscribe anytime.

Join