Case Study | Budget Management | Capacity Planning

Managing a $500K+ L&D Budget When You Are Never Fully Staffed

TL;DR I managed a $500K+ annual L&D budget while the function was rarely funded at the full headcount level requested. The work was to turn capacity pressure into a clear business conversation: what work could be done, what risk increased, what tradeoffs leaders were accepting, and where technology or process could reduce load.
Download one-pager Read the story

The challenge

The team had more work than the approved staffing model could comfortably support. Headcount requests were often partially approved, usually around 60 to 70 percent of the ask.

That meant I had to manage two truths at once. The team needed more capacity, and the business needed disciplined tradeoffs.

The budget conversation had to move beyond "we are busy." It needed evidence.

The approach

I built budget conversations around capacity, risk, and tradeoff. What can the team deliver? What will slow down? What quality risk increases? What can tools, vendors, or process changes offset?

I also learned to show the cost of saying no. Leaders need to understand the consequence of partial funding in practical terms.

The goal was to make each decision informed enough that the tradeoff was visible.

Downloadable takeaway

A one-page version of the model with the decision questions, sequence, metrics, and red flags someone can use after reading the case.

Download PDF

What I built

Built capacity evidence

I tied staffing asks to intake volume, production work, LMS administration, stakeholder demand, and quality expectations.

This made it easier to explain why one additional role changed throughput or risk.

Used tradeoff language

When requests were partially approved, I documented what the team could do and what would be delayed or deprioritized.

That kept the conversation tied to business choices instead of general frustration.

Reduced pressure where possible

Process improvements, AI-assisted work, and clearer review rules helped reduce administrative burden.

Those offsets mattered because the team still had to deliver while capacity was constrained.

Operating artifacts

These are sanitized work-product examples. They show the kind of artifact I would expect the team to use. They are sanitized and exclude confidential company material.

Capacity model Budget

Budget Capacity Ledger

Demand Modules, programs, LMS work, stakeholder requests.
Capacity Available FTE, contractor support, tool automation.
Tradeoff Delay, reduce scope, accept risk, or fund support.

Budget Capacity Ledger

A simple view of demand, capacity, and tradeoff.

Business case Budget

Headcount Request One-Pager

Problem Demand exceeds current role capacity.
Impact Launch delay, quality risk, maintenance backlog.
Decision Fund role, change scope, or accept timeline.

Headcount Request One-Pager

The argument leaders need when approving or denying the request.

Tradeoff Budget

Partial Approval Decision Log

Approved Critical role or tool funded.
Deferred Lower-value work or maintenance backlog.
Mitigated AI, workflow simplification, vendor support.

Partial Approval Decision Log

A record of what changed when only part of the request was funded.

The results

$500K+ Annual L&D budget managed over four and a half years.
60-70% Typical headcount approval range against requested staffing.
23% Administrative burden reduction while operating at reduced capacity.
12x Content output growth without proportional headcount increase.

The operating insight

Budget work gets stronger when it is tied to capacity math and business tradeoffs. A leader may still say no, but the no should be informed.

The out-of-the-box move was using the cost of no as part of the business case. That keeps partial approval from pretending nothing changes.

What this proves

  • I can manage L&D budget pressure with business discipline.
  • I know how to connect headcount, tools, process, quality, and delivery risk.
  • I can keep delivery moving while making tradeoffs visible.
← Previous: Customer Learning Quality Next: Programs →