Stop Proving Leadership ROI. Start Demonstrating It.

When budgets get squeezed, leadership development is often first to be questioned. It's also one of the hardest to defend because, for too long, it's been judged on how it felt rather than what it changed. If you sponsor, buy or experience development, you're part of that story. Here's a more strategic way to approach it.

"Proof" is the wrong promise

Most leadership outcomes have more than one cause. Sales rise after a programme, but the market may have lifted too. Engagement improves, but a new director may have arrived. If you claim your programme caused the result, a sceptical CFO will pull the claim apart, and your credibility with it.

A stronger position is contribution. Be open about it: here's what shifted, here's how we know, and here's what else was going on. That honesty doesn't dilute the case. It makes it more believable, and it keeps you out of the trap of proving something your data can't support.

Try this: In your next development report, add a short section called "Other factors at play". Describe the wider context, then explain the contribution you believe the development made.

It's your budget, so it's your story

It's easy to assume that demonstrating impact belongs to HR or finance. It doesn't. If you're a people leader who has backed coaching for a team member, you've made an investment decision, and the money has come out of your budget.

Owning that story does two things. It sharpens your commercial awareness, which matters most in large, matrixed organisations where day-to-day impact is hard to see. It also builds a virtuous spiral. When development is held to account, it stops being dismissed as a "soft skill" exercise, and it becomes easier to protect when times are hard.

Try this: For each development investment you've sponsored, write a two-sentence value story. What changed, and what did that make possible for the business? If you can't write it, that's your first finding.

Start with the objective, not the programme

The most important work happens before anything is delivered. "Our leaders need to be better" isn't an objective. It's a hope. The clearer you are about the behaviours that need to change, and how those connect to strategy, the easier everything downstream becomes, including measurement.

This is also your best protection against buying the wrong thing. A sponsor who loves coaching may commission it for everyone, when actually only four people out of 500 might need one-to-one support. A lighter touch may be effective for the rest. Rushing this stage risks wasting money, and some providers will be happy to let you.

Try this: Write one sentence that links your next development spend to a specific strategic objective. If you can't draw that red thread from organisational goal to individual behaviour, pause before you commit the budget.

Measure first, then design

You can't show movement without a starting point. Before designing anything, build a baseline. That might be an employee survey or a training needs analysis, but behavioural data is more powerful still. A 360 that compares how leaders rate themselves with how others experience them reveals where the gaps are, and where they're widest.

That insight does more than set a benchmark. It shows you which teams need what, so you can meet leaders where they are rather than pushing everyone through the same programme. One-size-fits-all approaches tend to work for nobody in particular, and they leak return on investment from day one.

Try this: Choose three behaviours that matter most to your strategy and gather a simple self and others view of each before you invest further. Even a short survey gives you something to compare against later.

Look beyond the happy sheet

Feedback gathered on the final afternoon of a workshop tells you people were energised and a bit tired. It's useful, but it isn't evidence of change. Not measuring at all is worse.

A simple framework still does the job well. Kirkpatrick's levels ask four plain questions: how was the experience, what was learned, what changed in behaviour, and what were the results? Jack Phillips, founder of the ROI Institute, later added a fifth level: commercial ROI. Treat ROI as part of the story rather than a silver bullet. It's harder to isolate, but it speaks the language of finance, and it protects the organisation by testing whether the solution was worth the spend.

Try this: For your current programme, name one measure at each of the four levels. If one level is empty, you've found your blind spot.

Give change time to show up

Value doesn't appear overnight. Capture reactions on the day, by all means, but add a pulse check around four weeks later. Ask what people committed to, what they've applied and what's got in the way. Comparing confidence levels before and after helps to strip out some of the bias of being fresh from a good session.

For lasting behaviour change, re-run your baseline at least six months after the learning ends, ideally with the same people. Expect a pattern that surprises you. Peer-visible behaviours tend to improve, while self-ratings often dip slightly as leaders recalibrate what good looks like. That narrowing gap isn't failure. It's a sign of rising self-awareness, and it's a strong part of your story.

Our previous article #111 ‘Self-Trust is a Performance Asset’ explores how leaders can build and calibrate it.

Try this: Put the six-month re-measure in the diary now, before the programme starts. Things that aren't scheduled rarely happen.

Be demanding of development

Good development should feel uncomfortable. It needs real stakes and genuine accountability, with leaders expected to do something with what they've learned.

The same standard should apply to the programme itself.

Sometimes development doesn't work, and that isn't always the provider's fault. Stuff happens. But, if you've measured well, you can have an informed conversation about why, rather than a vague complaint that a lot of money seems to have vanished. Being demanding of your suppliers, and of your own organisation, is how you keep development in the good books.

Try this: Ask your current provider two questions this week. What will you measure, and when will you report back? Their answers will tell you a lot about how seriously they take accountability.

At Exigence, we help organisations build development that's designed to be measured from day one, from the 360 baseline through to long-term behavioural change, so you can show the value with confidence. That’s the thinking behind Trace, our framework built to do just that. Find out more here.