Last time, this series took a hundred individual skill trajectories and read them together, until a talent map appeared where a performance report used to be. It showed where capability concentrates, where it is thinning, and which critical skill hangs on a single person nobody had noticed. That is a genuinely useful picture. But a picture is not a decision, and the next obstacle is rarely analytical. It is a meeting, usually the one where the budget gets set, and it is where good evidence most often goes to be politely ignored.
L&D has a long habit of walking into that meeting with activity: courses delivered, completions logged, hours consumed, satisfaction scores. Finance does not read those as evidence of anything except spend. The talent map changes what can be brought through the door, but only if it is translated from the language of learning into the language of risk, capacity and cost. This post is about making that translation.
Activity Is Not an Argument
A completion rate answers a question the finance director never asked. They are not wondering whether people finished the course; they are wondering what the organisation gets for the money and what happens if the money is withheld. An activity report cannot answer either, because it describes what L&D did rather than what changed in the business. A request built on it sounds like a department asking to continue because it exists, and it is usually treated accordingly: flat, trimmed, or quietly cut when the quarter tightens.
Two cycles of evidenced skills data offer something structurally different. They describe the workforce, not the department: which capabilities the strategy depends on, how many people hold them, and which direction those numbers are moving. The question on the table stops being whether training is worth funding and becomes whether the organisation is comfortable with what its own data says about its position.
Lead With the Exposure, Not the Programme
The strongest opening in a budget conversation is a specific, named exposure. Not “we need leadership development funding”, but “the platform migration depends on a skill held by two people, one of whom has been flat for two cycles, and there is no third.” That sentence can be checked, it has a number inside it, and it describes a cost of doing nothing in terms any executive recognises: delay, dependency and replacement risk.
This is where the
analytics and reporting view earns its keep. The aim is not a bigger dashboard. It is the two or three charts that isolate a concentration or a thinning in a skill the business has already said it cares about. Everything else, however interesting, belongs in an appendix. A budget meeting has room for one clear exposure, and it is better to land one than to gesture at ten.
Attach a Proposal That Is Small Enough to Believe
Once the exposure is on the table, the temptation is to answer it with a grand programme. Resist it. Decision-makers trust requests that are proportionate to the problem and bounded in time, and distrust anything that reads as a framework in search of a budget. A better shape is an explicit goal, a named group of people, a defined window, and a measure that the next assessment cycle will settle one way or the other.
That is precisely the job of structured
training goals: a stated target for a specific skill and a specific population, tied to the evidence that justified it. Framed this way, the request is also falsifiable. If the next cycle shows the skill rising where funding was applied, the case for the following year is already written. If it does not, the organisation has learned something cheaply, and the credibility of the person who said so in advance goes up rather than down.
Show the Cost of the Alternatives
Executives rarely choose between a proposal and nothing. They choose between a proposal and the other ways of closing the same gap, usually hiring externally or accepting the risk. Treat those honestly in the paper. External hiring is sometimes the right answer for a skill the organisation has no foundation to grow, and saying so builds more trust than pretending development always wins. Where there is a rising internal base to build on, the comparison tends to favour development on speed and retention, but it should be allowed to favour the other side when it does.
Delivery cost belongs in the same honest ledger. Content that can be built and refreshed quickly changes the arithmetic, which is why the economics of
course creation and management are worth stating plainly instead of leaving finance to assume the slowest, most expensive version of the work. A proposal that has already priced its own delivery is much harder to dismiss than one that leaves that number open.
What Changes After the First Time
The first evidence-led budget conversation is the hardest, because the room is used to a different kind of paper. The second is easier, because there is now a prior cycle to point to: a goal that was set, funded and measured, with a result nobody had to take on trust. Over a few rounds the relationship with finance shifts from defending a cost line to reporting on a capability position, which is a much better place for L&D to be standing.
The practical instruction is short, and it follows from everything this series has built. Do not carry the talent map into the meeting as a finding to admire. Carry it as an exposure, a bounded proposal, an honest comparison, and a date on which the next cycle will say whether it worked. Evidence that comes with its own test is the kind a budget meeting can actually act on.
