The AI Skills Gap You’re Measuring Is the Wrong One

I’ve watched this exact mistake happen four times in twenty years, and I suspect I’m about to watch it happen a fifth.

The first time was learning management systems, the platforms companies bought in the 2000s to centralize training and prove compliance. The second was virtual instructor-led training, when travel budgets got cut and every classroom session moved onto a WebEx call, still measured by attendance instead of anything that happened back on the job. The third was mobile learning, pitched hard to corporate audiences who mostly treated it as a pilot program that never scaled, while deskless and frontline workers never got a pitch at all. They just started using their phones on shift, because a phone was the only device most of them had access to during the workday. Now it’s AI. Four completely different technologies, twenty years apart, and every rollout got measured the same wrong way: completions, certifications, an adoption number by end of quarter.

Every time, the numbers looked fine on paper. Eighteen months later, the tool would be sitting half used, sometimes less, and the explanation was always the same: the workforce wasn’t ready.

It was never a readiness problem. The training measured whether someone could operate the tool in a pre-defined exercise. It never measured whether anyone had a reason to reach for it on a Tuesday when something in their actual job was stuck. Organizations kept building for the first one while the second one was the entire point.

On the rollouts that did work, someone found the moment in a role where the tool solved a real problem, showed one person the exact fix, and let word of mouth do more than the course catalog ever could. Adoption wasn’t a training outcome. It was a proximity outcome, how close the tool sat to a problem someone already had.

I met Bob Mosher and Conrad Gottfredson in 2007, at the Masie Center, hosted by Elliott Masie, watching them argue this exact point years before most companies had a mobile strategy, let alone an AI one. Their 5 Moments of Need framework names the moment rollouts keep missing: the Solve moment, when someone hits a real problem and needs help right then, not in a course scheduled for next Tuesday. Most AI training gets built for the “New” moment, telling people a tool exists, while the payoff sits in Solve and Apply, putting the tool where the work already is. Same fight, different tool.

The AI conversation right now is repeating the pattern. Companies stand up literacy curricula, track completions, publish adoption percentages, and treat a low number as evidence employees need more training or incentives. Meanwhile, people doing frontline and operational work are already finding their own uses for AI tools that help them, often without telling anyone, because nobody told them it was allowed or pointed them at where it would help.

That’s not a skills gap. That’s a translation gap, one level above the workforce, not inside it. The technology gets purchased. The harder work, connecting it to specific jobs and moments, is a separate project that doesn’t always get built. Completing a course tells you nothing about whether someone now has a reason to use what they learned. Those two numbers can move in opposite directions, and most dashboards can’t tell the difference.

There’s a deeper cost here beyond the software budget. When a translation gap gets mistaken for a skills problem, the response for the next rollout tends to repeat: more training, more completions tracked, tighter certification. That response gets more confident with each wave, right as the actual fix, connecting the tool to the work, gets no easier to find, because nobody built a discipline for finding it.

Twenty years, four technology waves, the same diagnosis missed every time. I don’t think that’s a coincidence, and I don’t think AI is going to be the wave that breaks the pattern on its own. It’s going to take someone in the room asking a different question before the rollout starts: not “how do we get people trained,” but “where exactly does this tool solve a problem someone already has, and how do we get it in front of them at that exact moment.”

I’d like to think the fifth time is the one we get ahead of, instead of explaining after the fact.