Microsoft is cutting thousands of jobs this month across sales, consulting, and Xbox, with reports putting the number near 5,700, while its AI infrastructure spend runs toward $190 billion this year. Earlier this year, a Writer survey of 2,400 knowledge workers and C-suite leaders found that 60% of companies plan to lay off employees who "can't or won't" adopt AI. Fifty-four percent of the C-suite executives surveyed said AI adoption is actively tearing their company apart.
Put those two data points next to each other and you get an uncomfortable question: how many of those layoffs are actually about AI, and how many are budget cuts wearing an AI costume because "AI adoption" is the one justification nobody in HR or legal knows how to push back on?
I don't think Microsoft is lying about where the money's going — $190 billion in capex is real and it has to come from somewhere. But "funding AI infrastructure" and "laid off for not adopting AI" are two different sentences, and companies are increasingly using them interchangeably. One is a budget reallocation. The other is a performance claim about a specific employee. Only one of those requires evidence.
"Didn't adopt AI" is not a metric. It's a vibe. Ask any of the 60% of companies in that Writer survey how they're actually measuring AI adoption, and you'll get answers like "usage of the tools we rolled out" or "engagement with the platform" — proxies that measure whether someone opened an app, not whether they got any better at their job because of it. We covered this exact gap a few days ago with GitHub Copilot's metered billing: token burn tells you someone's using the tool, not whether they're any good with it. The same blind spot applies here, at a much higher stakes level.
You can't fire someone for "not adopting AI" on the same evidentiary standard you'd use to justify a real performance action, and most companies aren't even trying to build that standard. They're building a narrative.
That matters because narratives crack under scrutiny; documented gaps don't. When the RIF hits and someone asks "why me," "you didn't adopt AI" is a sentence that sounds decisive right up until someone asks what that meant, measured how, against what baseline. Most companies making this claim right now couldn't answer that question in a deposition. The people whose actual job is measuring this admit the numbers aren't there. Forrester's J.P. Gownder, after talking with more than 200 companies about their AI programs, put the underlying problem plainly:
"The vast majority of over 200 clients I have spoken with have struggled to define and quantify any noticeable financial return on investment from AI technology."
— J.P. Gownder, Vice President and Principal Analyst, Forrester, SHRM
If the companies deploying AI can't quantify what it did for the business, no manager can credibly quantify what one employee's "adoption" of it was worth. And this isn't far-fetched: wrongful termination suits tied to vague AI-adoption justifications are exactly the kind of claim that's cheap to file and expensive to defend when the underlying metric was never real.
What you do about all this depends on which side of the layoff you're standing on.
If you're a CTO or VP genuinely trying to reshape your team around AI-fluent people — and some of you are, this isn't all pretext — the fix is the same one we've been pushing all year: define the coefficient before you use it as a cause. What does "adopted AI" mean in your org, concretely, for this role? Is it shipped output per engineer at a given AI-credit spend? Is it a documented before/after on cycle time? Is it a skills assessment with a rubric someone could defend? If you can't answer that in one sentence with a number attached, you don't have an AI-adoption problem to solve with layoffs.
You have a headcount budget problem you're dressing up, and your best people, the ones actually good with these tools, will clock the difference immediately. They talk to each other. A vague AI-adoption justification for cuts reads, correctly, as "we don't actually know who's good, we're just cutting."
The flip side is where the opportunity is. Every company running this playbook sloppily is about to release people who got cut on a narrative rather than a number, including plenty who are genuinely strong and just didn't work somewhere that measured anything real. If you're hiring, the AI-adoption layoffs happening right now are a sourcing signal, not just a headline. The candidates worth calling aren't the ones who survived the cut. They're the ones who can tell you, unprompted, exactly how they used AI tools to change their output, with specifics rather than buzzwords, regardless of which side of a badly-run layoff they landed on.
The companies that get this right in the next twelve months are the ones that build a real measurement before they build the justification. Everyone else is going to find out the hard way that "AI adoption" isn't a defense. It's a claim, and claims need receipts.
VC5 Consulting helps technology companies build and scale engineering teams. We work with CTOs and technical founders on staffing strategy, compensation benchmarking, and talent pipeline development. If you're trying to figure out what "AI-fluent" actually means for your roles — before you make a headcount decision based on it — let's talk.