Only 7% of technology leaders say they have the skills required to complete their top projects, and 65% report that their teams need additional training. These two numbers in combination describe something specific: the gap is not primarily a headcount gap. It is a skills currency gap — the people are partially there, but their skills are not current enough, or specific enough, or deep enough, for the work the organisation needs to do in 2026.
What the 93% Gap Actually Looks Like in Practice
The gap manifests differently depending on which strategic initiative is being prioritised, and understanding the specific manifestation is the starting point for addressing it effectively rather than generically.
For AI implementation projects — the most common source of the gap in 2026 — the problem is typically not a complete absence of AI capability. Most organisations have developers who have experimented with AI tools, data scientists who understand ML concepts, and product managers who can describe AI-enhanced features. What they lack is the production deployment expertise to take those concepts and experiments into systems that run reliably, securely, and at the scale the business requires. That specific capability is rare, commands a significant compensation premium, and cannot be developed from scratch in the timeframe that most AI initiatives require.
For cybersecurity and NIS2 compliance obligations, the gap is typically in specialisation depth rather than awareness. Teams understand that they need better security. They may even understand the specific NIS2 requirements that apply to their organisation. What they lack is the technical depth to implement the required controls — cloud security architecture, incident response capability, governance and compliance documentation — at the standard that regulatory enforcement will scrutinise.
For cloud infrastructure modernisation, the gap is often in the transition from understanding how cloud works to being able to architect and manage complex, multi-service, multi-account cloud environments that meet enterprise reliability, cost management, and security standards simultaneously.
The Three Responses That Are Actually Working
The 93% of technology leaders managing a skills gap in 2026 are not passive about it. They are pursuing three approaches, often simultaneously, with varying degrees of success depending on how well each is executed.
Targeted external hiring
The first is targeted external hiring for the specific skills that cannot be developed internally in the available timeframe. This sounds obvious, but the precision required is higher than most hiring briefs achieve. The difference between “we need a cloud engineer” and “we need someone who can architect a multi-account AWS environment with compliance controls meeting our NIS2 scope requirements, integrated with our existing identity management infrastructure” is the difference between a brief that sources a commodity and a brief that sources a solution. Precision in the brief determines whether external hiring addresses the gap or adds headcount without closing it.
Structured upskilling
The second is structured upskilling of existing team members in the specific capability gaps identified. 65% of technology leaders report that their teams need additional training — and the organisations closing gaps fastest are those that have identified specific training targets rather than general development budgets. An engineer spending six focused months on cloud security architecture certification, with applied project work alongside, develops a capability that can begin contributing within the training period. A team with a general learning and development budget and no specific target rarely produces the same result. BrainSource
External specialist
The third is external specialist engagement for project-specific work that cannot wait for internal capability to develop or for permanent hiring to complete. AI implementation consultants, fractional security architects, and cloud migration specialists who can deliver a defined output in a defined timeframe are being engaged at higher volumes in 2026 than at any point in the preceding five years — precisely because the gap between what organisations need and what their current teams can deliver is real, urgent, and commercially consequential.
Why Generic Upskilling Programmes Are Not Closing the Gap
The instinct to respond to a skills gap with a training programme is natural and frequently correct. The execution, however, is where most organisations lose the benefit. Generic training programmes — broad technology learning platforms, general AI literacy courses, enterprise-wide digital skills initiatives — produce awareness rather than capability. They are valuable for cultural alignment and for establishing a baseline understanding of emerging technologies. They do not produce the specific technical depth required to architect an AI system, implement a NIS2-compliant security programme, or manage a multi-cloud environment at enterprise scale.
The organisations closing skills gaps most effectively in 2026 are those that have accepted the precision requirement. The training investment is targeted at specific individuals who are already closest to the required capability, on specific skills that are directly applicable to the projects in progress, with applied project work that tests and extends the learning in real conditions. The output is measured not by training completion certificates but by the point at which the individual begins producing output at the required standard.
This requires more upfront investment in skills gap analysis — identifying precisely where the gap sits, which individuals are closest to closing it, and what the specific learning pathway looks like — than most organisations are accustomed to making. It also requires coordination between the training investment and the project plan, so that the learning pathway is timed to deliver capability when it is needed rather than when the course calendar is convenient.
The Recruitment Role in a Skills-Gap-First Strategy
For the specific capability gaps that cannot be closed through upskilling within the required timeframe, external recruitment is the mechanism — and the precision required in the brief is directly proportional to the specificity of the gap. A gap in cloud security architecture requires a recruiter who can evaluate whether a candidate’s AWS security certification reflects genuine architectural depth or surface-level knowledge. A gap in AI production deployment requires a recruiter who understands the difference between ML research experience and MLOps engineering capability.
This is the core reason that specialist recruiters outperform generalists on the specific hiring challenges that the 93% gap creates. The brief for a skills-gap-driven hire is inherently precise and technical. Executing against it requires domain expertise at the recruiter level — the ability to assess candidates against criteria that are not legible in a job title or a credential list.
