Dispatches
Essays··9 min read

Mandates without mastery: the AI upskilling gap that vendor dashboards hide

Corporate AI mandates — Google tying usage to performance reviews, Meta tracking AI-assisted output, Microsoft declaring it non-optional — now outrun demonstrable capability. Eighty-two per cent of organisations provide AI training; 59% still report a skills gap. The deficit is not access — completion certificates measure the wrong thing, and firms are applying one-time training models to a skill that demands continuous, deliberate practice on realistic tasks.

Google began factoring AI use into software engineer performance reviews in the first quarter of 2026, and Meta overhauled its evaluation process to track how many lines of code engineers produce with AI assistance

.

At Microsoft, using AI on the job is 'no longer optional', and at Meta, 'AI-driven impact' is now a 'core expectation'

. The enforcement push is unambiguous. The productivity gains promised for three years are now being measured—in quarterly reviews, in compensation bands, and in who survives the next re-org.

But the data beneath those mandates is ugly.

A 2026 DataCamp enterprise leader survey reports that 82% of organizations provide some form of AI training, yet 59% still report an AI skills gap

.

Deloitte found that whilst worker access to AI tools expanded by 50% in a single year, fewer than 60% of employees with access actually use AI in their daily workflow

. The gap is not access—it is application. Companies gave people the tools. Many did not pick them up. Those who did often lack the judgment to use them well.

I have spent eighteen months advising three European banks, a national health service, and two industrial manufacturers on production AI deployments. The pattern is consistent: vendor pilots that look excellent in controlled conditions collapse when applied to real operational tempo by people who completed a self-paced Udemy course. The issue is not intelligence—it is that we are trying to industrialise a skill (prompt-informed judgment, output verification, hallucination detection) using training models designed for software that had a manual.

The mandates are real, the capability is not

IDC estimates that sustained skills shortages may cost the global economy up to $5.5 trillion by 2026 in product delays, quality issues, missed revenue, and impaired competitiveness; over 90% of global enterprises are projected to face critical skills shortages by 2026

.

A Study.com survey published in April 2026 found that 62% of employers struggle to find candidates with AI-related skills

.

The US Department of Labor saw the writing on the wall.

On 24 March 2026, the department launched 'Make America AI-Ready', a free AI literacy course delivered entirely via text message, designed for daily 10-minute engagement over seven days—part of the administration's commitment to equip American workers with foundational AI skills

.

The department's broader registered apprenticeship initiative, announced in April 2026, explicitly states that 'AI is transforming every industry, and our workforce systems must evolve just as quickly', focusing on embedding AI training, tools, and curricula into existing apprenticeship programs

.

European regulators went further.

Article 4 of the EU AI Act, which entered into application on 2 February 2025, requires providers and deployers of AI systems to ensure a sufficient level of AI literacy of their staff and other persons dealing with AI systems on their behalf

. This is not guidance—it is a legal obligation with supervision and enforcement in the remit of national market surveillance authorities. The EU has drawn a line: if you deploy AI in a regulated context, your people must be demonstrably competent.

The divergence between US enforcement (performance reviews, compensation signals) and European enforcement (regulatory obligation) points to the same underlying reality: voluntary uptake has failed. Firms spent two years making AI "available" and discovered that availability does not produce capability.

Why training completion rates are a vanity metric

Corporate training programs have a well-documented problem: completion rates look good, but skill transfer to real work is poor—especially acute in AI and data science, where the application gap between 'I watched the video' and 'I can build this for our data' is enormous

.

Most organizations are not ignoring AI training entirely—only 35% of leaders report having a mature, organization-wide AI upskilling program—but access to training does not automatically translate into capability

.

I have seen the pattern in three continents. A Fortune 500 client spent €4.2 million on a Coursera enterprise licence, tracked course completions (excellent numbers, 73% engagement), then struggled to find anyone who could build a working RAG pipeline for their legal department's contract review process. The course taught the theory; it did not teach how to debug a vector database when semantic search returns garbage because your embedding model was never fine-tuned for German regulatory language.

Trained employees are 2.7 times more proficient than self-taught workers, and formal AI training programs deliver measurable ROI of $3.70 per dollar invested

—but those figures come from vendors with economic interest in continued spend. What they omit is the denominator: proficient at what, measured how, and how many trained employees never apply the skill in production?

BCG projects that over the next two to three years, 50% to 55% of jobs in the US will be reshaped by AI; for many employees, this will mean they retain the same or similar role but face radically new expectations for how they work and what they produce, requiring a scaled strategic approach to upskilling, reskilling, and the restructuring of career ladders

. The work is not being automated—it is being augmented in ways that require continuous re-learning, and we are applying one-time training paradigms to a moving target.

What deliberate practice looks like when autocomplete is always on

Gartner's strategic predictions warn that atrophy of critical-thinking skills due to GenAI use will push 50% of organizations to require 'AI-free' skills assessments by 2026

. That is not technophobia—it is pattern recognition. When the tool always offers a suggestion, the cognitive load required to evaluate that suggestion atrophies unless you design for it.

JLL's AI@JLL Learning Series demonstrated a 146.15% higher adoption rate for employees who received training versus those who did not, with one use case reducing manual work from four hours to 15 minutes—a 93.75% reduction in time to task

. That is a genuine result. But note what it measures: adoption rate and task time, not judgment quality, error rate, or whether the output meets regulatory or contractual standard without human correction.

The centaur model—human judgment paired with machine output—depends on the human being able to evaluate the output. That requires domain expertise that predates the tooling.

Among BCG's 'future-built companies', 88% of managers actively role model AI use and incorporate it into decision-making and daily operations, versus 25% at AI laggards

. The gap is not tool access—it is management behaviour that signals what matters.

In the firms I work with, the employees who extract real value from LLMs are those who already knew how to break a problem into subtasks, verify sources, and distinguish plausible from correct. The model gives them speed. It does not give them the skill to assess its output. That skill must be taught—not in a six-week bootcamp, but through structured practice on realistic tasks with feedback loops and an error budget.

We have no industrial-scale pedagogy for this yet.

Slalom's 2026 AI Research Report found that 68% of leaders and employees say they can keep pace with AI, yet 93% report that workforce barriers such as underdeveloped skills and inadequate training limit their progress

. That is not a skills gap—it is a self-assessment failure. People believe they are competent because they received a certificate, not because they have repeatedly applied the skill under realistic constraints.

What I would do if I were on your board

If I were advising your executive team, I would push for three uncomfortable moves:

Stop conflating access, training, and capability. Instrument actual usage on production tasks, not logins or course completions. Measure error rate, time-to-correction, and whether output ships without human rework.

Tracking whether employees use AI tools is straightforward; measuring whether they use them well is not—lines of code written with AI assistance say little about quality, strategic thinking, or the judgment required to know when AI output needs correction, and HR teams will need rubrics that distinguish genuine fluency from surface-level compliance

.

Redesign work before you mandate the tool.

Companies are mandating AI use whilst simultaneously failing to redesign work around it—84% of organizations have not restructured jobs or workflows around AI capabilities, even as insufficient worker skills rank as the top barrier to AI integration

. You cannot measure "AI-driven impact" if the role, the approval process, the tooling, and the incentive structure were designed for pre-LLM workflows. Fix the process, then add the model.

Budget for continuous upskilling, not one-time programs.

Organizations should budget $2,000–5,000 per employee for comprehensive AI upskilling, and OpenAI's 2025 State of Enterprise AI report documents a 6× productivity gap between power users and average employees using the same tools—closing that gap requires continuous proficiency development, not a one-time session

. The model will change; the API will change; the regulatory posture will change. If your upskilling budget is a 2026 line item rather than a perpetual operating cost, you are planning to fail in 2027.

I would also insist on role-differentiated tracks.

A data analyst, a business operations manager, and a software engineer all need AI literacy, but they need it at different depths and applied to different contexts—effective programs offer tiered curricula rather than one-size-fits-all courses

. A procurement officer does not need to understand transformer architecture; they need to know when a contract summary from an LLM has hallucinated a termination clause. Training that does not map to job tasks is training that will not transfer.

The firms that will win in this cycle are not those with the largest training catalogues—they are those that have embedded AI literacy into operational rhythm, rebuilt approval processes to tolerate model error within guardrails, and hired or developed people who can assess model output faster than the model can generate it. That is not a training problem. It is a change-management problem with a training component.

The mandates will not slow down.

General Assembly's State of Tech Talent 2026 survey of 500 HR leaders found that 83% believe company success depends more on upskilling existing employees for AI than on hiring new talent, yet low employee buy-in and low leadership buy-in remain the top barriers to training programs actually taking hold

. If your training completion rates look strong but your production AI usage remains weak, the gap is not motivation—it is that you are measuring the wrong thing.

Build for mastery, not for dashboards. The next re-org will not ask how many courses your people finished—it will ask what they shipped, how fast, and whether it required three rounds of human correction before it was fit for purpose. That is the exam. Everything else is theatre.


Tarry Singh is the founder and CEO of Real AI (realai.eu), an enterprise AI advisory and deployment firm working with global enterprises on production agent systems, model risk, and AI sovereignty strategy. He also leads Earthscan (earthscan.io) for Energy AI, and is a founding contributor to the EU-funded HCAIM and PANORAIMA programmes for responsible AI education across European universities. He writes at tarrysingh.com.

Cartouche
Mandates without mastery: the AI upskilling gap that vendor dashboards hide · Dispatches, 7 July 2026 · T. Singh