How to build a learning and development strategy that survives budget season

13 October 2026

Build a learning and development strategy that holds up. Compare design models, choose delivery methods, set governance, and measure real impact.

White outline of Goldie, the SurveyMonkey mascot

Learning and development budgets are cut first and defended worst. Not because training does not work, but because most L&D functions can report attendance and satisfaction and nothing that a finance director recognises as evidence.

This guide is the structural build. Needs assessment, choice of design model, delivery decisions, governance and budget ownership, alignment to career ladders, and an evaluation approach that produces defensible numbers.

Measure skill gaps, learning impact, and career outcomes in one connected feedback program.

A learning and development strategy is a multi-year structure that defines which capabilities the organisation needs, who owns building them, how programs are designed and funded, and how effectiveness is judged. A training plan is the schedule of activity that a strategy produces.

The difference shows up under pressure. Ask a training plan why a leadership course exists and you get "we run it every autumn." Ask a strategy and you get a capability gap, a named owner, a delivery choice, a budget, and an evaluation target.

The case for investing at all is well established and covered elsewhere, so read why L&D drives employee engagement if you still need to build that argument. Everything below assumes the argument is won and the question is how to build the thing.

Every credible L&D strategy documents the same five components:

  1. Capability thesis. The specific skills the business will need in 18 to 36 months, and where you are short.
  2. Design model. The single framework you use to build programs, so quality does not depend on who built each one.
  3. Delivery portfolio. Which modalities you use for which learning types, with cost and reach documented.
  4. Governance and funding. Who decides what gets built, who pays, and who signs off on retiring a program.
  5. Measurement frame. The levels at which you evaluate and the thresholds that trigger redesign.

If any one of those is undocumented, that is where your strategy will fail under scrutiny. Missing governance is the most common gap, and it is the reason programs accumulate and never retire.

Find out which skills your people want to build and where they see their next step.

A needs assessment establishes the gap between the capabilities your strategy requires and the capabilities you have. It is the step that separates a strategy from a shopping list, and it is the step most often replaced with a manager wish-list exercise.

Run it at three levels, because a gap at one level demands a completely different response than the same gap at another.

  • Organisational. Which capabilities does the business strategy require that we do not currently have at sufficient depth. Sources: strategic plan, workforce plan, and the roles you consistently hire externally because you cannot fill them internally.
  • Role and team. Which competencies does each role family need at each level, and where are the concentrations of shortfall. Sources: manager assessment, performance data, and skills inventories.
  • Individual. Which skills does each person need for current performance and their next step. Sources: self-assessment, manager assessment, and career-aspiration data.

Only the individual level requires asking employees directly, but skipping that level is what produces programs nobody attends. People opt into learning that serves a goal they hold, and you cannot infer that goal from a competency matrix.

The instrument that carries most of the weight is a skills-gap survey with three paired parts. Keep it under 10 minutes or completion will collapse in the roles you most need to hear from.

Structure it like this:

  1. Current capability. Self-rating against a defined competency list, on a behavioural scale rather than a confidence scale. Ask what the person can do unsupervised, not how confident they feel.
  2. Importance to the role. Have the same respondent rate how much each competency matters to doing their job well. The gap between importance and capability is your priority score.
  3. Desired development. Ask which competencies the person wants to build and why, including whether the motive is current performance, promotion, or a lateral move.

Then run the same competency list past managers for their teams. The divergence between self-rating and manager rating is itself a finding, and a large systematic gap in one function usually points at a calibration problem rather than a skills problem.

Score each competency gap on three factors and rank: size of gap, strategic importance, and population affected. A large gap in a competency that matters little is not a priority, however uncomfortable the score looks on a heat map.

Two further filters keep the list honest. Discard gaps that training cannot close, because a capability shortfall caused by tooling, staffing, or unclear process will not respond to a course. And separate build-versus-buy explicitly, because some capabilities are faster and cheaper to hire than to develop.

Segmenting the results matters as much as collecting them. Woom Bikes found that learning preferences differed by region across a 30-country footprint, which changed program design rather than program content.

As April Obersteller, Managing Director at Woom Bikes, put it:


With SurveyMonkey learning and development surveys, we were able to see what things landed and what things didn't. And as a global organization, we found that our teams in different parts of the world had different preferences when it comes to learning. That allowed us to customize our programs to the audience we were trying to serve.

A design model is the repeatable method your team uses to build every program. Choosing one deliberately matters because it determines where your effort goes, what your programs look like, and which failure modes you are exposed to.

Three models cover most organisations. They are not interchangeable, and picking by familiarity rather than by fit is a common and expensive mistake.

70-20-10 is an allocation heuristic: roughly 70% of development comes from challenging on-the-job experience, 20% from relationships and feedback, and 10% from formal instruction. Its value is that it forces you to design the 90% that most L&D functions ignore.

It suits organisations where the constraint is opportunity rather than content, and where managers are capable of designing stretch work. It fails where manager capability is weak, because the 70% becomes unstructured exposure with no learning attached, and where the ratios get treated as targets rather than as a reminder.

ADDIE is a five-phase instructional design process: analysis, design, development, implementation, and evaluation. It produces consistent, well-structured programs and a clear audit trail, which matters in regulated environments.

It suits compliance training, technical certification, and any context where content must be identical for every learner and defensible to an auditor. It fails where speed matters, because a full ADDIE cycle is slow, and where the subject is changing faster than you can complete the cycle.

The 4E model organises development across education, experience, exposure, and environment. Its distinguishing move is treating environment as a design variable, meaning the conditions, incentives, and tooling that determine whether new capability actually gets used.

It suits culture and behaviour change programs, where instruction alone reliably fails. It is harder to govern than ADDIE, because three of the four Es are owned outside L&D and require negotiated commitments from other functions.

ModelBest fitMain strengthMain failure mode
70-20-10Leadership and general capability building where opportunity is the constraint.Forces design of experience and feedback, not just courses.Ratios treated as targets; unstructured 70% with weak managers.
ADDIECompliance, technical, and certification content.Consistency, rigor, and an auditable trail.Too slow for fast-changing subjects; over-engineered for soft skills.
4EBehavior and culture change programs.Treats environment and incentives as part of the design.Hard to govern; depends on commitments from other functions.

You can run more than one, but not per program at the whim of the designer. Assign a model per program category and document the assignment, so quality does not vary with who happened to build the thing.

Delivery choice is where L&D budgets are won and lost, because the cost spread between modalities is an order of magnitude and the effectiveness spread depends entirely on learning type. Cohort-based live facilitation is expensive and unmatched for practice-and-feedback learning. Self-paced digital is cheap, scales infinitely, and is close to worthless for behaviour change.

Decide by learning type first, then by constraint.

Learning typePrimary modalityWhy it fitsCost and scale profile
Knowledge acquisitionSelf-paced digital, with a knowledge check.Content is stable and transfer is testable.Low cost, unlimited scale.
Procedural and technical skillGuided practice with simulation or sandbox.Requires repetition with correction.Medium cost, medium scale.
Interpersonal and managerial skillCohort-based live sessions with practice and peer feedback.Needs live reaction and observed behavior.High cost, limited scale.
Judgement and decision-makingStructured on-the-job assignment with a coach.Only develops against real consequence.High cost, very limited scale.
Compliance and policySelf-paced digital with mandatory assessment.Consistency and auditability outrank engagement.Low cost, unlimited scale.
Tacit and organizational knowledgePeer learning, communities of practice, shadowing.Knowledge is not documentable.Low direct cost, high coordination cost.

Four constraints legitimately force a downgrade from the ideal modality:

  • Geographic spread and time zones, which make synchronous cohorts expensive or exclusionary.
  • Shift and frontline patterns, where employees have no protected learning time during a shift.
  • Language and accessibility requirements, which raise the cost of live delivery sharply.
  • Release cadence, where content changes faster than you can rebuild a facilitated program.

When you downgrade, record the trade-off. A compromise you documented is a decision. A compromise you forgot is why the program scored badly and nobody could explain it.

Modality preference is measurable and it varies by population more than most teams expect. Ask about format preference, preferred session length, and protected time availability in the same survey as your skills gap items, and segment the answers by function, level, region, and shift pattern.

Governance is the component that keeps a strategy alive between leadership changes. Without it, L&D becomes a request queue, programs accumulate, and nothing is ever retired.

Write down who holds each of these five rights, by name or role:

  1. Prioritisation. Who decides which capability gaps get funded this cycle.
  2. Design approval. Who signs off that a program meets the design standard before build.
  3. Funding. Whether budget sits centrally, with business units, or split, and who approves exceptions.
  4. Participation mandate. Who can make a program mandatory, and who protects the time.
  5. Retirement. Who can kill a program, and on what evidence.

Retirement rights are the ones nobody assigns and the ones that determine whether your portfolio stays coherent. Set a standing rule that every program is reviewed against its evaluation targets annually and either recommitted or retired.

  • Fully central. Consistency and buying power, but weak business-unit ownership and low perceived relevance.
  • Fully devolved. High relevance and ownership, but duplication, inconsistent quality, and no capacity to fund enterprise capability.
  • Hybrid. Central funding for enterprise capability and compliance, devolved funding for function-specific needs. More administration, best incentive alignment.

Hybrid is the common answer for organisations above a few hundred employees. The critical detail is a published split rule, because an unwritten one gets relitigated every planning cycle.

Name the obligation, not just the stakeholder. An L&D steering group that meets without commitments attached is a status meeting.

  • Executive sponsor. Protects budget, arbitrates priority conflicts, and holds business units to their commitments.
  • Business-unit leaders. Validate capability gaps, release people for learning time, and own adoption in their area.
  • People managers. Design the on-the-job component, hold development conversations, and reinforce new behaviour.
  • HR business partners. Connect L&D to performance, succession, and workforce planning.
  • Finance. Agrees the evaluation standard in advance, so the measurement argument is settled before the results arrive.

That last point is the one that saves budgets. Agreeing what would count as evidence, with finance, before you build anything, removes the most common way a successful program gets cut.

An L&D portfolio that is not mapped to career structure produces a catalogue of courses with no answer to the only question employees actually ask, which is what this gets me. Alignment means every program is attached to a defined level transition or a documented role requirement.

Lay your career structure and your program portfolio side by side, then mark every cell:

  1. List the level transitions. For each role family, the move from each level to the next.
  2. Name the capability delta. What a person must be able to do at the higher level that they did not need before.
  3. Attach a program or mark a gap. Which existing program develops that delta, or note that nothing does.
  4. Flag the orphans. programs that map to no transition and no role requirement. These are your retirement candidates.

The orphan list is usually uncomfortable and usually right. programs survive on habit, and a mapping exercise is the least political way to surface that.

This exercise needs a career structure to map to. If your levels are undefined or your advancement criteria are informal, no L&D alignment is possible, because there is no transition to develop people toward. Build the structural layer first using a career pathing framework, then return to mapping.

Woom Bikes illustrates the end state. After running engagement and learning surveys, leadership established individual "ride plans" for employee career growth, which is what program-to-path alignment looks like once the structure exists. Their targeted learning surveys drove satisfaction with internal development programs to 86%.

Alignment only produces motivation if employees can see it. Publish the map: for each role and level, the transition ahead, the capability delta, and the specific programs that develop it.

A published map also reduces demand on managers, who otherwise spend development conversations reconstructing information that should be documented. It reduces the promotion-path anxiety that drives strong people to look outside for their next step, which is worth reading about in the context of skills-based organisation design.

Attendance and satisfaction are the two metrics every L&D function has and the two that convince nobody. A defensible measurement frame evaluates at multiple levels and commits to thresholds in advance.

The Kirkpatrick model gives the standard four levels, with a fifth commonly added from Phillips for financial return. Evaluate at level one and two for every program, and at three and four only for programs where the cost justifies the measurement effort.

  1. Reaction. Did learners find it relevant and well delivered. Cheap, immediate, and weakly predictive of anything.
  2. Learning. Did knowledge or skill change. Measured with pre- and post-assessment or a scored quiz.
  3. Behaviour. Did on-the-job behaviour change. Measured 30, 60, and 90 days out, ideally with manager and peer input.
  4. Results. Did the business indicator the program targeted move. Requires a named metric agreed before launch.
  5. Return. Did the benefit exceed the cost. Requires defensible attribution and is worth attempting only for large programs.

Level three is where most measurement programs stop being done and start being talked about. It is also the level that produces the evidence finance accepts, because behaviour change 90 days after a course is the first point at which something real has happened.

Four instruments cover the five levels, and they are worth building once and reusing:

  • Post-session survey for reaction, kept to five items so completion stays high.
  • Pre- and post-assessment or quiz for learning, using the same items both times.
  • 30, 60, and 90-day follow-up for behaviour, sent to the learner and their manager with matched items.
  • Linked business metric for results, pulled from the system that already owns it rather than self-reported.

Connect these as one program rather than four disconnected surveys, so you can trend a cohort across all four instruments. Multi-survey analysis is what makes that comparison possible without manual data assembly, and shared dashboards are how business-unit leaders see their own cohort results without waiting for a quarterly deck.

Commit to thresholds before launch, and to what you will do at each outcome. Without a pre-committed threshold, every result gets interpreted favourably and nothing is ever redesigned.

A workable rule set:

  1. Below threshold on learning. Redesign the content or the assessment. The problem is instructional.
  2. Passes learning, fails behaviour. The problem is transfer, meaning environment, manager reinforcement, or opportunity. Fix conditions, not content.
  3. Passes behaviour, fails results. The capability thesis was wrong. Revisit the needs assessment rather than the program.
  4. Fails on two consecutive cycles. Retire, and reallocate the budget to a gap on the priority list.

The analysis burden is the practical limiter on all of this, particularly the open-text feedback where the useful explanations live. In SurveyMonkey customer research, 93% of HR professionals agreed the platform frees up their time to focus on more strategic work, and 96% agreed it increased their confidence in creating a survey.

The SurveyMonkey features that carry an L&D measurement frame are quizzes for knowledge testing, 25+ question types for pre- and post-assessment design, Programs for the 30, 60, and 90-day cadence, multi-survey analysis for trending a cohort across instruments, thematic and sentiment analysis for open text, and integrations that let you embed a survey link directly in your learning platform.

Once your measurement frame is running, the next build is usually the content itself. Read the practical guide to creating employee training that holds up against these evaluation levels.

Smiling HR employee holding a piece of paper and taking a video call on laptop

Create powerful HR surveys with SurveyMonkey to gather feedback, boost engagement, and improve workplace culture. Streamline HR processes with customizable templates.

A man and woman looking at an article on their laptop, and writing information on sticky notes

Design a career pathing framework your team trusts. Map role families, levels, and skills ladders, then validate them with employee survey data.

Smiling man with glasses using a laptop

Build an employee benefits strategy from real survey data, with benefits questions, a prioritization method, and feedback loops that keep it honest.

Woman reviewing information on her laptop

Run a workplace culture assessment across psychological safety, belonging, values, and trust, and score results to see where culture really differs.