The displacement gap

Every few weeks a new headline lands: 85 million jobs displaced. 300 million full-time roles affected. All white-collar work automated within 18 months. The numbers are big, round, and — if you look closely — mostly about theoretical capability, not observed reality.

Anthropic published labor market research in March that introduced a distinction most coverage ignores: the gap between what AI can automate and what it is automating. That gap is enormous. And it tells a very different story than the headlines.

The gap is the story

Anthropic’s key contribution is a measure they call “observed exposure” — what Claude actually does in production, as opposed to what benchmarks say it could do.

The numbers are striking. Computer and math occupations have 94% theoretical AI exposure. In practice, Claude covers 33%. Office and admin roles — the ones everyone assumes are already gone — show 90% theoretical exposure and a fraction of that in actual use.

97% of observed Claude usage falls within theoretically feasible categories. The model can do the work. Organizations just aren’t deploying it that way.

This is not a technology constraint. It is an adoption constraint. The bottleneck is not whether the model can draft a financial analysis or triage a support ticket. It is whether the organization has rebuilt the workflow, retrained the team, and instrumented the process to actually use AI where it fits.

Mustafa Suleyman predicted in February that all white-collar tasks would be automated within 12-18 months. Anthropic’s data says we’re at a third of theoretical capacity today, with no clear acceleration in the adoption curve. Both things can be true — the capability is there, the deployment is not — but the implication is different from what the headlines suggest.

The hollowing-out is real, just quiet

No clear evidence that AI has increased overall unemployment. That’s the headline finding, and it’s technically correct. But underneath it, something more specific is happening.

Anthropic found a 14% drop in the job-finding rate for workers aged 22-25 in AI-exposed occupations since ChatGPT launched. Not mass layoffs — reduced hiring. The entry-level pipeline is narrowing. Companies are not firing customer service reps. They are not backfilling them when they leave.

This is the pattern that matters for anyone running an AI program. The displacement is not dramatic. It is a slow compression of roles at the bottom of the org chart — data entry, basic admin, junior financial analysis, first-tier customer support. The people in these roles are not losing their jobs tomorrow. They are losing the next version of their jobs — the promotion, the adjacent role, the career ladder that used to exist.

US data suggests roughly 25,000 jobs erased per month against 9,000 new ones created. A net loss of 16,000 per month sounds alarming until you put it against a labor force of 160 million. But zoom in on who’s affected and the picture sharpens: entry-level workers, administrative roles, and — disproportionately — women.

The gender gap nobody is planning for

79% of employed US women work in roles at high risk of automation, compared to 58% of men. Of the 6 million US workers most directly exposed to AI displacement, more than 85% are women. The ILO found women more exposed than men in 88% of countries analyzed.

This is not a coincidence. Women are overrepresented in exactly the categories AI automates first: administrative support, clerical work, payroll, reception, data entry. These roles have high theoretical exposure and high observed exposure — the gap between capability and deployment is smaller here because the tasks are more structured, more repetitive, and easier to automate without rebuilding an entire workflow.

Harvard and Berkeley researchers found a 25% gap in AI adoption between men and women. The workers most exposed to displacement are also the least likely to be building fluency with the tools that could reshape their roles instead of eliminating them.

Most workforce planning we see treats AI displacement as role-neutral. It is not. If your reskilling program does not specifically account for which roles and which demographics are most exposed, you are planning for a workforce transition that does not match the actual transition happening.

Reskilling is not a slide in the deck

IBM estimates 40% of the global workforce needs new skills within three years. The WEF projects 92 million jobs disappearing by 2030, offset by 170 million new roles — but those new roles require different skills, and the people losing the old roles are not automatically qualified for the new ones.

The new jobs are real. AI trainers, explainability engineers, data annotators, forward-deployed AI engineers — 1.3 million new roles by various estimates, plus 600,000 data center positions. Workers with advanced AI skills earn 56% more than peers. The demand side is genuine.

The problem is the bridge. BCG and HBR frame it well: AI will reshape more jobs than it replaces. 50-55% of US jobs will be substantially changed, not eliminated. But “substantially changed” means the person in the role needs to learn new tools, adopt new workflows, and develop judgment about when to trust AI output and when to override it. That is a training problem. And 90% of global enterprises report critical skills shortages going into 2026.

We see this pattern in every engagement. The organization has a model in production. The AI team is shipping features. But nobody owns the question of how the people whose workflows just changed are supposed to adapt. There is no training program. There is no measurement of whether adoption is happening at the individual level. There is a Slack message that says “we now have an AI tool for X” and an expectation that people will figure it out.

They don’t.

Three phases, one window

The research broadly converges on a phased timeline. 2023-2025 was task automation, hiring freezes, role compression. 2026-2028 — where we are now — is when career transition spikes and displacement peaks. 2028 onward is the new equilibrium, where the job market has restructured around AI-augmented roles.

If that timeline is roughly right, organizations have about two years to get serious about the workforce side of their AI programs. Not the model side. Not the infrastructure side. The people side.

That means identifying which roles are being compressed — not theoretically, but based on actual usage data. It means building reskilling programs targeted at the specific demographics and job families most exposed. It means measuring adoption at the individual level, not the org level, because a 60% adoption rate can mean 60% of the team uses AI daily or 100% of the team opened the tool once. Those are very different situations.

The heuristic

Your AI workforce problem is not that machines will replace your people. It is that you are changing what the work requires without changing how your people are prepared to do it. Close that gap before the market closes it for you.

tl;dr

The pattern. Organizations focus on what AI can automate in theory while ignoring that actual deployment is a fraction of capability — and the real displacement is a quiet hollowing-out of entry-level and administrative roles, disproportionately affecting women. The fix. Treat reskilling as an engineering problem: identify which roles are actually changing based on usage data, build targeted training for the specific demographics most exposed, and measure adoption at the individual level. The outcome. Your workforce adapts alongside your AI program instead of being hollowed out by it, and the people most at risk become the people most prepared for what comes next.