Most learning programs don't stall because nobody wants them. They stall because the person who needs to build the thing looks at what it will actually take, counts the people available to do it, and realizes the two numbers don't match.
It is a familiar moment. Leadership has approved the budget. The business case is solid. And then you start listing out the work, and you find three or four skills your team simply doesn't have in the room.
This happens more often than most L&D leaders admit, and it is rarely a reflection of the team. It is a reflection of how specialized learning work has become.
When the skills are not in the room, there are three realistic options: hire the capability permanently, outsource the program to an external partner, or augment the existing team with specialists for the length of the project. The right choice depends on how long the skill will be needed, who needs to own the finished program, and how soon it has to be live.
The rest of this piece looks at what a learning program genuinely requires, where the gaps usually appear, and how to decide between those three routes.
What a Learning Program Actually Requires
Before you can work out what is missing, it helps to be honest about the full list of what a program needs. The work is almost always broader than the original plan accounts for.
A typical program calls on most of the following:
- Learning strategy. Someone who can translate a business problem into a learning problem, and who knows when training is not the answer at all.
- Instructional design. The person who structures the experience, decides what learners do rather than what they are shown, and builds assessment that means something.
- Learning experience design. Increasingly its own discipline, focused on how the program feels to move through rather than how it is organized.
- Content development. Building the thing in the authoring tool, which is a genuine craft and not a formality.
- Media. Video, animation, graphics, voiceover. This is where timelines quietly stretch.
- Technology. LMS or LXP configuration, integrations, reporting setup, and the testing nobody budgets for.
- Project management. Someone holding the schedule, the stakeholders, and the review cycles together.
- Measurement. Deciding before launch what success looks like, and building the means to observe it.
Very few internal teams carry all eight. Most carry three or four well, borrow one or two from elsewhere in the business, and discover the rest partway through.
Where the Gaps Usually Show Up
The shortfall is rarely in the obvious places. Teams tend to be reasonably strong on design and development, because that is what they were hired to do.
The gaps appear at the edges.
Specialist subject knowledge. A compliance program in a regulated industry, a clinical skills program, a technical certification. These need someone who understands the subject deeply enough to ask the right questions of your experts, and that person is hard to find on short notice.
Emerging capability. AI governance, prompt design, data and learning analytics. These skills barely existed as job titles a few years ago. Hiring for them permanently means betting on what the role will look like in three years, which is a difficult bet to place.
Capacity at the peak. Sometimes the skill exists on the team, but the person holding it is already committed to something else. A capability gap and a capacity gap feel identical when you are the one staring at a deadline.
Measurement. Almost every team says it wants better evidence of impact, and almost none has someone whose actual job is to produce it.
Noticing which of these you are facing matters, because it changes the answer. A capacity problem and a capability problem call for different responses.
Three Ways to Close the Gap
There are really only three, and each one is right in different circumstances.
Hiring Permanently
The strongest option when the need is ongoing. If you will be building programs of this kind every year, bringing the skill in-house means it compounds. The person learns your business, your stakeholders, and your systems, and that institutional knowledge becomes genuinely valuable over time.
The constraint is time and certainty. Recruiting a specialist takes months, and that is before onboarding. You are also committing to the role for the long term, which is reasonable when the need is permanent and expensive when it is not.
Choose this when: the capability is central to your strategy and the work will keep coming.
Outsourcing the Program
Handing the whole thing to a partner who designs and builds it end to end. This works well when the program is self-contained, when you need it delivered rather than developed alongside you, and when your team genuinely has no bandwidth to participate.
The trade-off is ownership. Knowledge tends to leave with the partner, and the next program starts from a similar position. That is fine for a one-off and less comfortable for something you will need to maintain and extend.
Choose this when: the program is discrete, the deadline is firm, and internal capacity is genuinely unavailable.
Augmenting the Team
Bringing in specialists who work inside your team for the length of the engagement. Your people keep ownership of the program and the relationships. The specialist contributes the skill that is missing.
This suits the situation most teams are actually in, which is having a capable team with one or two specific holes. It is also faster than hiring, because providers who focus on L&D staff augmentation maintain a standing network rather than starting a search from scratch. And it keeps knowledge in the building, because the work happens alongside the existing team rather than elsewhere.
The trade-off is that it requires management. Someone internal has to brief well, integrate the person properly, and stay involved. Augmentation is not a way to stop thinking about the program.
Choose this when: your team can lead the work but cannot do all of it, or when the capability need is real but not yet permanent.
Deciding Between Them
Four questions usually settle it.
How long will you need this skill? Permanent need points to hiring. Project-length need points to augmentation. One-off points to outsourcing.
Who needs to own the result? If your team will maintain and extend the program, keep them at the center and bring support to them. If it genuinely sits outside your remit, outsourcing is cleaner.
When does it have to be live? Hiring takes months. If the date is fixed and close, that option quietly removes itself.
Is this a skills problem or a bandwidth problem? A capacity gap can sometimes be solved by resequencing the work. A capability gap cannot.
It is worth answering these honestly before you start looking. Teams that skip this step often end up hiring permanently for a six-month need, or outsourcing something they will have to maintain themselves for years.
Knowing Which Specialists You Actually Need
Once the route is decided, the next question is who specifically to bring in, and this is where a lot of briefs go vague.
"We need an instructional designer" covers an enormous range. An ID who builds compliance modules and an ID who designs immersive scenario work are not interchangeable, and neither is a learning strategist who shapes the program at the front end. The same applies to LMS administrators, learning experience designers and media specialists.
It is worth being specific before you approach anyone. Most established L&D talent providers publish the specialist roles they work across, which is a useful way to sharpen a brief even before you decide who to approach. A tight brief gets you a better shortlist and a much shorter search.
One Thing Worth Protecting
Whatever route you take, protect the strategy work.
It is tempting to treat strategy as the part your team can handle internally, and bring in help for the production work that feels more technical. In practice this is often backwards. Production can be scoped and briefed. Strategy depends on knowing the business, the audience, and the constraint you are actually solving for, and that is the part most worth having experienced judgment on.
If you can only bring in one specialist, consider making it the person who helps you decide what to build rather than the person who builds it.
Building With What You Have, Plus What You Need
Not having every skill in-house is normal. It is not a sign of a weak team, and it is certainly not a reason to narrow the program down to what the current roster can deliver.
There is also no barrier to quality. Blended teams of internal and external specialists produce work that stands up against anything built entirely in-house, and the industry awards each year are full of programs built exactly that way. The 2026 Brandon Hall Group HCM Excellence Awards, for example, recognized 24 programs from SweetRush and its client-partners, 17 of them Gold.
The programs that succeed tend to come from leaders who were realistic early about the gaps, honest about which kind of gap they were facing, and deliberate about how to close it. That assessment is unglamorous work, and it is the part that decides whether the program ships.
