If budget costs are looking imminent, rather than draw up a list of redundancies, Ryan Austin suggests looking to see where other costs can be improved. Explore three overlooked operational levers that can absorb a mandated cost-reduction target before headcount has changes, grounded in operational data from enterprise L&D functions.
For three years, the L&D budget conversation has followed the same script: costs are flat or shrinking, demand is rising, and AI is supposed to close the gap. It has closed part of it, content that used to take weeks now takes days. But speed was never where most of the money was leaking.
Of the $130 billion invested annually in learning programs, less than 25% is judged to be effective
When a Chief Financial Officer hands down a mandated cost-reduction target, L&D usually assumes it’s a headcount conversation. It’s an understandable reflex: headcount is the fastest lever to pull, and the easiest line for a CFO to see on a spreadsheet. It’s also usually the most expensive lever in the medium term. Cutting people removes delivery capacity precisely when demand keeps rising. Also factor in that the capacity comes back more slowly and at higher cost than it left, through backfill hiring, onboarding time, and lost institutional knowledge.
An analysis of operational data (LearnOps) across dozens of enterprise L&D functions, spanning close to 9,000 projects, nearly 8,000 intake requests, and more than 60,000 tasks across two consecutive quarters in 2026, all point to three cost levers most L&D teams haven’t touched yet. Unlike headcount, each of these levers can be sized and reported in the same finance-friendly terms a CFO already understands, without emptying the room first.
1. Fix prioritisation before you fix headcount
The most common hidden cost in L&D isn’t a program that fails. It’s a project that never should have started in the first place, sitting in the system consuming hours, attention, and reporting cycles with no clear line back to a business goal.
Across the data set reviewed, the share of active projects carrying no assigned priority level rose from 22.7% to 34.2% in a single quarter, meaning more than a third of active work had no documented basis for being ranked against anything else competing for the team’s time.
In the same window, request approval rates slipped from 85.4% to 82.7% even as request volume held steady, a sign that a growing backlog is forming behind a triage process that isn’t keeping pace with demand.
This is the least visible of the three levers and the easiest to defend to a CFO, because it doesn’t touch a single existing program. It only stops new, unranked work from entering the queue.
- Score before you schedule
Every intake request should answer three questions before it’s assigned:
1) What business goal does this ladder to?
2) What happens if it’s not done?
3) Who owns the outcome?
Requests that can’t answer these should sit in a parking lot, not a project plan. - Put a number on the backlog
Multiply the average task-hours consumed by un-prioritised work by a blended hourly cost, and CFOs can see exactly how many hours, and therefore how much budget, are tied up in work with no strategic justification. - Report the ratio, not just the volume
A rising share of unprioritised work is a leading indicator of budget risk long before it shows up as an overrun. Track it quarterly alongside approval rates.
Tip: If a request can’t be scored against a 1-year, 3-year, or 5-year business priority, it goes on a waitlist, not a work plan. This single rule is usually enough to cut 15–20% of low-value intake before it ever consumes a resourcing hour.
2. Close the capacity-visibility gap before you assume overrun
When leadership looks for savings, the instinct is to hunt for programs that ran over budget. The data usually tells a different story, and a more useful one.
Across the same data set, the share of tasks where logged hours came in under the original estimate rose from 62.9% to 77.5% quarter over quarter, with the typical gap between estimated and logged hours widening substantially. It would be easy to read this as a sign that teams are becoming dramatically more efficient. The more plausible explanation, and the one leadership should act on, is that time-tracking discipline degrades on the tail end of delivery: work gets finished, but the hours spent finishing it never get logged.
This matters because a CFO who is later shown “efficiency gains” built on incomplete time data will eventually find the gap, and the L&D function’s credibility goes with it. The fix isn’t a bigger budget ask. It’s a smaller, cheaper one: close the visibility gap so that whatever the real efficiency number turns out to be, it’s one leadership can trust.
- Treat logging discipline as a governance metric, not an HR nag
Track the percentage of completed tasks with logged actual hours as its own KPI, separate from delivery performance. - Audit before you report
Before publishing any capacity or efficiency figure externally or to the executive team, spot-check a sample of “under budget” tasks against the actual delivery timeline. - Don’t let a data-quality problem masquerade as a program-quality win
If the real number is less flattering than the reported one, find that out internally first.
3. Redistribute work before you backfill it
The third lever is the one CFOs feel first when it goes wrong, because it eventually shows up as attrition, and attrition shows up as a hiring cost.
In the data reviewed, the number of people actively logging work on L&D tasks fell by roughly 12% quarter over quarter, while total hours logged across the function held essentially flat. The result: the average number of tasks carried per L&D team member roughly doubled, and the share of total task volume sitting with the busiest 10% of contributors climbed from 49% to 65%. The same amount of output is now moving through fewer hands, a pattern that precedes burnout-driven attrition far more often than it precedes a genuine efficiency story.
At the same time, the composition of demand hitting L&D teams is shifting in a way that compounds the problem. Requests classified as advisory or consulting work nearly doubled as a share of total intake, and assessment and evaluation requests grew as well, while pure learning-delivery requests shrank. L&D is being asked to do more strategic, higher-skill work with fewer, more concentrated hands doing it — the opposite of what a cost-reduction mandate should look like on paper.
- Map concentration before you plan capacity
Identify the small group of contributors carrying a disproportionate share of active work and treat their bandwidth as a governance risk, not a compliment to their productivity. - Redeploy before you requisition
A rebalancing of existing workload across underused capacity is a faster, cheaper first move than opening a new headcount request, and it’s the move a CFO will always ask whether you’ve already made. - Size the true cost of concentration
If the busiest 10% of a team is carrying two-thirds of the workload, model what backfill hiring would cost if even one of those people leaves. That number, not a headcount request, is usually the more persuasive board slide.
Case in point: A mid-sized financial services firm facing a mandated group-wide cost-reduction target initially proposed a 15% reduction in its L&D team. A review of its own operational data showed that 40% of active projects had no assigned priority, and two contributors were carrying more active tasks than the rest of the team combined. Re-scoring the backlog and rebalancing workload absorbed roughly two-thirds of the mandated savings target without a single role being eliminated — and the remaining gap was closed through a smaller, defensible reduction in low-priority vendor spend rather than headcount.
If headcount still has to move
None of this is an argument that headcount reductions are never warranted. Sometimes the mandated number is larger than these three levers can absorb on their own. What changes is the conversation that follows.
An L&D leader who walks into that conversation having already quantified unprioritised work, closed the reporting-integrity gap, and rebalanced concentrated workload is negotiating from evidence, not from a defensive crouch. The remaining ask of whether it’s a smaller headcount reduction, a vendor renegotiation, or a longer runway to hit the target, is easier to make credibly once the other levers are visibly exhausted.
The same discipline that surfaces these levers also protects the function if a reduction does happen. A team that can show precisely which work is prioritised, how time is actually being spent, and where capacity is concentrated is far better positioned to demonstrate what gets deprioritised or delayed as a direct, traceable consequence of a smaller team — rather than simply absorbing the cut and hoping quality doesn’t visibly slip.
The bigger shift
Cost-cutting mandates land on L&D the same way they land on every other function, and pretending otherwise doesn’t help anyone hit their number. But the data suggests the reflex response, headcount, is usually the least examined option, not the only one.
Prioritisation discipline, reporting integrity, and workload distribution are unglamorous levers. They don’t make for an exciting town hall slide. They are, however, the levers a CFO can actually verify, size, and trust — which makes them the ones worth pulling first.
Ryan Austin is Founder and CEO of Cognota
