How to address capability gaps with effective training

A capability gap is the distance between what your team can currently do and what your strategy needs it to do. It covers named technical skills as well as behaviours like judgement, communication and leading others, and it is not the same thing as a capacity gap, where the ability exists but the hours do not. Closing one starts with an honest diagnosis, because training aimed at the wrong gap burns budget and changes nothing.

Last reviewed September 2026.

What is a capability gap?

Capability is what a team can reliably deliver under normal conditions. A capability gap is the shortfall between that and the work ahead, expressed as something observable. "Better communication" is not a gap. "Nobody on the team can run a structured commercial negotiation without the general manager in the room" is a gap, because you can see when it closes.

Gaps show up in three places that are easy to miss. Some are technical, where a tool, method or qualification is missing. Some are behavioural, where the skill exists but the person avoids the situation that calls for it. Some are structural, where the work is spread across people who each hold a fragment and nobody owns the whole thing. Training reliably helps with the first, sometimes helps with the second, and almost never helps with the third.

There is a retention cost to leaving them open. People who cannot see a path to grow inside an organisation eventually look for one outside it, and visible investment in development is one of the stronger retention levers a leader has without touching salary.

Capability gap, skill gap, capacity gap and coverage gap

These four terms get used interchangeably in planning meetings, which is how a capacity problem ends up on a training plan. They call for different responses, so it is worth separating them before anyone books a course.

Capacity gap analysis is the one most often mislabelled. If your team is producing good work and simply cannot produce enough of it, a course will make the problem worse for the fortnight everyone is out of the office.

How to run a capability gap analysis

The analysis has two layers, and skipping the second is why so many training plans miss. Start with the technical layer, working backwards from the strategy rather than forwards from what people already do.

• List the outcomes the next 12 months require. Not projects, outcomes. "Win and deliver two enterprise contracts" rather than "run the enterprise program".
• Write the capabilities each outcome depends on. Keep them observable. If you cannot describe what good looks like in a sentence, you cannot assess it.
• Rate the current level honestly, by evidence. A skills matrix that records who has actually done the work, not who attended the session, is the right instrument here.
• Mark each gap for impact and urgency. Some gaps are uncomfortable. Only some of them are blocking delivery this year.

The second layer is the shape of the team. Compono's research into high-performing teams shows that eight kinds of work need covering, from pioneering through to auditing, and that individuals have genuine preferences among them. Some gaps turn out to be coverage gaps rather than skill gaps, where nobody is naturally drawn to a whole category of work. Training a reluctant Pioneer to enjoy compliance detail is a losing bet. Bringing in an Auditor, or handing that work to the person who finds it satisfying, fixes it in a week.

If you want a rough size on the cost of the gaps before you argue for budget, the skills gap analysis calculator gives you a figure to put in the business case, and the step-by-step guide to conducting a skills gap analysis covers the technical layer in more depth.

How to plan training based on the skill gaps you found

Once the gaps are mapped, sequencing decides the return. Spreading budget evenly across every gap produces a lot of half-finished courses and no visible change. Rank by whether closing the gap unblocks delivery, then by how many people the gap affects, then by how long the training takes to show up in the work.

Here is a prioritisation pass using illustrative numbers rather than benchmarks. A team finds four gaps. Gap A blocks a contract worth real revenue and affects two people. Gap B affects twelve people but nothing depends on it this year. Gap C affects one person and closes in a fortnight. Gap D is a capacity gap wearing a training costume. Sequencing A, then C, then B, and removing D from the plan entirely, moves the delivery risk in the first month. Funding all four equally moves nothing until the following quarter.

Delivery format matters as much as the content. Training sticks when it matches how someone prefers to learn and work. A Campaigner tends to do well in a collaborative, high-energy workshop. An Auditor often prefers a methodical module they can work through alone and revisit. Give both the same three-day offsite and one of them quietly disengages by the first afternoon.

Build practice into the plan rather than ending at the course. A capability closes when somebody does the real work, gets feedback on it, and does it again. Scheduling the first real application within two weeks of the training is the cheapest thing you can do to protect the investment.

When training is the wrong answer

Three situations come up often enough to check for before approving a budget. A capacity gap needs hours, not learning. A coverage gap needs a different person in the mix. A gap caused by unclear accountability, where three people each assume someone else owns the outcome, needs a decision from a leader and no training at all.

This is also where the system you use starts to matter. Compono Develop connects capability data with learning delivery, so leaders can see where the gaps sit, assign learning that matches each person's profile, and track whether the gap is actually closing rather than whether the module was completed. If you are weighing whether that belongs in a dedicated platform or inside your core people system, the comparison of an LMS against an HRIS sets out where each one stops.

How to prove the gap is closing

Completion rates are a vanity metric. They record attendance. The measure that matters is whether the team can now do the thing it could not do before: the negotiation gets run without the general manager, the analysis gets produced in-house, the handover stops leaking. Define that observable outcome while you are designing the training, not afterwards, because retrofitting a measure onto finished training almost always produces a flattering one.

Re-assess on a rhythm rather than on alarm. Team composition changes, strategy shifts, and yesterday's closed gap reopens with one resignation. A capability review every six months keeps the budget pointed at what is blocking work now, and it gives people a visible path for growth, which feeds back into retention.

Frequently asked questions

What is a capability gap?

A capability gap is the difference between what your team can currently do and what your strategy requires. It covers technical skills alongside behaviours such as communication, judgement and leading others, and it includes coverage gaps where nobody naturally owns a whole category of work.

What is the difference between a capability gap and a capacity gap?

A capability gap means the ability is missing. A capacity gap means the ability is there but the hours or the headcount are not. The giveaway is quality: with a capacity gap the finished work is good and there is simply not enough of it, so reprioritising, automating or adding people fixes it rather than training.

How do I identify capability gaps in my team?

Work backwards from the outcomes the next 12 months require, write down the capabilities each outcome depends on, then rate the current level against evidence of work actually done. Add a view of team shape on top, so you can tell a skill gap apart from a category of work nobody is drawn to.

How do I plan training based on skill gaps?

Rank the gaps by whether closing them unblocks delivery, then by how many people they affect, then by how quickly the training shows up in the work. Fund the top of that list properly instead of spreading budget evenly, match the delivery format to how each person prefers to learn, and schedule the first real application within a fortnight.

How do I measure whether the training worked?

Define the observable outcome before the training starts, then check for it afterwards. Completion rates tell you people finished a course. The real test is whether the team can now perform the task it previously could not, under normal conditions and without a rescue.