What Finally Makes a Sponsor Say Yes
Somewhere in every HR leader's inbox is the email that started it.
Not a business case. Not a slide with a leadership pipeline diagram and a line trending politely up and to the right. Something smaller. A resignation letter from someone they'd quietly assumed would be running a department in three years. A comment from a board member, dropped almost in passing, about why engagement dipped the same quarter a well-liked manager left. A 1:1 that went sideways when a rising star said, flatly, that they didn't want their manager's job — because they'd spent two years watching what the job did to their manager.
None of these moments make it into a leadership development proposal. They're the reason someone sits down to write one.
The Business Case Comes After, Not Before
Ask a sponsor why they funded a leadership program, and you'll usually get a clean answer. Retention risk. Succession gaps. A benchmark against what competitors are spending on development. Numbers, cited with confidence.
Ask when they actually decided, and the story gets less tidy. Most sponsors can point to a specific week. Sometimes a specific conversation. The business case — the slide with the cost-of-turnover math, the competitor benchmark, the projected ROI — usually gets built afterward. Not to convince themselves. To convince everyone else who wasn't in the room when the decision actually happened.
That gap matters more than it looks. It means the real trigger and the official justification are often two different things, and only one of them tells you what the sponsor actually needs the program to fix.
The Moments That Actually Trigger It
Talk to enough sponsors and a pattern shows up, even though no two stories sound alike on the surface.
One is the departure. Not any resignation — the one that stings, from someone the organization had quietly bet on. It forces an uncomfortable question: did we lose them, or did their manager?
Another is the derailment. A high performer gets promoted into management, and within two quarters the team that used to run well starts to wobble. Nobody did anything wrong exactly. The person just wasn't given anything beyond a title and good intentions.
The third is harder to name because it usually arrives as a single sentence, not an event. A line in an exit interview. A comment in a town hall that goes quiet for a second too long. Someone finally says, in a room where it can't be unheard, what the organization has half-known for a while.
Each of these lands differently depending on who's sitting in the sponsor's chair. But they share something: none of them are about training. They're about a specific person, a specific team, a specific moment where the cost of doing nothing became impossible to ignore.
What the Number on the Slide Is Actually For
Here's what's easy to miss: the ROI slide isn't for the sponsor. By the time it exists, the sponsor has already decided. The slide is for the people the sponsor now has to convince — a CFO who wants to see the math, a peer on the leadership team who's skeptical of anything that smells like a soft-skills initiative, a board that expects numbers attached to spend.
This is worth sitting with, because it changes what the slide needs to do. It doesn't need to persuade the person presenting it. It needs to survive contact with someone who wasn't there for the moment that made the decision feel obvious — someone who will ask, reasonably, how you know this will work.
Why This Matters for How a Program Gets Built
If the real trigger is a moment, not a strategy, then a generic leadership curriculum is answering the wrong question. The sponsor didn't wake up wanting to expose forty managers to feedback theory. They wanted to stop losing people like the one who just left. They wanted the next promoted manager to not repeat what just went wrong.
A program that ignores this ends up measuring the wrong things — satisfaction scores, completion rates, module counts. A program built with this in mind starts somewhere else: what was the moment, who was it about, and what would have to be different for that sponsor to feel, six months later, like the decision was right.
That's a different design question than "what should managers learn." It's closer to: what does this sponsor need to be able to say, the next time someone in the boardroom asks if it's working.
In the next article: the question that follows almost every sponsor a few months in — "is this actually working?" — and why it's harder to answer honestly than most programs are built to allow.