.png){kind=icon}
March 3, 2026
A pattern we've noticed across planning conversations this year: leaders know they have a skills gap. That part isn't new. What's shifted is the nature of the gap itself — and most capability strategies haven't adjusted to reflect it.
Two years ago, the dominant conversation was about technical skills. Could the workforce use the new platform? Did the team understand the data tools? Was AI literacy sufficient? Organisations responded by building training catalogues, licensing content libraries, and rolling out modules at scale. In many cases, it worked. Technical literacy improved. Completion rates were healthy. Boxes were ticked.
But the gap didn't close. It moved.
IDC projects that 90% of global enterprises will face critical skills shortages by 2026, with a cumulative cost to the global economy of $5.5 trillion. The World Economic Forum reports that 63% of employers identify skills gaps as the single biggest barrier to business transformation — and estimates that six in ten workers will need reskilling before 2027.
Those numbers are large enough to be easy to set aside as abstract. What makes them worth sitting with is what's underneath them.
The TalentLMS 2026 L&D Benchmark Report — which tracks year-over-year trends across thousands of HR leaders and employees — describes a notable shift in where the gap sits. Their finding: the old skills gap in technical literacy is narrowing. What's replacing it is a gap in leadership, strategic thinking, and adaptability. The higher-order capabilities that determine whether technology investment actually translates into performance.
McKinsey's Development in the Future of Work report reaches the same conclusion. Two-thirds of global executives they surveyed plan to prioritise what they describe as "uniquely human" capabilities — problem-solving, adaptability, collaboration. Not because technical skills don't matter, but because the organisations that have closed their technical gaps are discovering that technical competence without human capability doesn't move the needle.
This aligns with what Deloitte found in their January 2026 study on high-performing teams. The teams that consistently outperform are distinguished not by their technology adoption but by six human capabilities: curiosity, emotional intelligence, resilience, divergent thinking, connected teaming, and informed agility. Those same teams use AI more frequently and get better outcomes from it — because the human capability was there first.
Where most organisations run into trouble is not in recognising the gap. It's in how they try to close it.
The default approach remains content. More courses. Broader catalogues. Faster rollouts. And the logic is understandable — if people lack skills, give them training. If the gap is wide, scale the training.
The difficulty is that capability doesn't work like content. You can teach someone a software tool in a half-day workshop and reasonably expect them to use it on Monday. You cannot teach someone strategic thinking, resilience under pressure, or the ability to lead a team through ambiguity in the same way. These capabilities develop through practice, feedback, reflection, and sustained support over time. They require structure around them — not just a learning management system, but a framework that connects individual development to team functioning to organisational outcomes.
Bersin's research underscores this. Fewer than 30% of development programs produce sustained behaviour change. The remaining 70% generate awareness — useful in the moment, but insufficient to shift how someone actually operates under real conditions.
This is what we mean when we talk about the difference between training and capability. Training is an input. Capability is an outcome. And the distance between the two is where most L&D investment gets lost.
We worked with a telecommunications provider during an $80 million capital transformation over three years. The organisation was navigating a cloud migration, integrating new platforms, and restructuring multiple functions simultaneously. The typical capability response would have been a training rollout — platform-specific modules, compliance content, technical upskilling.
What they chose to do instead was build a capability architecture. Before designing any development, they baselined their entire workforce — assessing not just what skills existed but where the gaps sat, how they connected to role requirements, and which ones would constrain the transformation if left unaddressed.
Within twelve months, 91% of the workforce had been baselined against the capability framework. That's not a completion rate on a course. That's a structural understanding of where capability sits across the entire organisation — and where it doesn't.
From there, development was designed around the gaps that mattered most. Not a catalogue of 1,200 available courses offered equally to everyone, but targeted interventions connected to the specific capability constraints the baseline had identified.
The results were measured. Employee engagement increased 8% during a period of significant organisational change — a time when engagement typically declines. Attrition improved meaningfully, producing $427,000 in avoided hiring costs. The mastery engagement score — a measure of whether employees feel they're growing in their roles — increased by 11.4%. The measured return was $272 per employee invested.
None of that came from adding more content to the learning platform. It came from knowing where the gaps were before trying to close them.
The reason the shift in the skills gap matters is practical, not theoretical. Organisations that continue to respond to a human capability gap with a content and training strategy will continue to see the pattern they've been seeing — high completion, low behaviour change, persistent gaps in the areas that affect execution.
The World Economic Forum estimates that 44% of workers' existing skills will be disrupted in the next five years. Deloitte reports that 71% of workers already perform work outside their formal job description. The half-life of professional skills continues to shrink. These are not conditions that a static training approach can address.
What they require is infrastructure. The ability to understand what capability exists across the organisation, where the gaps sit, how those gaps connect to strategic priorities, and whether development activity is actually closing them. Not as a one-off audit, but as an ongoing rhythm that adapts as the work changes.
IDC's own research points to this directly. They note that 40% of IT leaders struggle with fragmented, inconsistent skills development across their organisations, leaving them unable to measure readiness. The organisations that move past this tend to share a common characteristic: they stopped treating capability as a training problem and started treating it as an operating system.
Most organisations acknowledge they face a skills gap. The research confirms it at scale. But the gap has shifted — from technical to human, from content to capability, from access to application.
The useful question for leaders reviewing their capability strategy this year may not be whether they have one. Most do. It may be whether the strategy is still designed around the gap that existed two years ago, or the one that the evidence now describes.
What does the organisation actually know about where capability sits today — not in completion rates, but in assessed, baselined, connected-to-outcomes terms? And is the development architecture designed to build the human capabilities that the research consistently identifies as the ones that determine whether everything else works?
Those are questions worth answering before the next training catalogue lands on someone's desk.
.jpg)
.jpg)
