Invest1 distinct publisher2 min readPublished
Project OT scoped cutting some teams by as much as 60 per cent and handing their work to AI agents. Meta executed a single 10 per cent layoff instead, after internal data showed the agents were not delivering the hoped-for productivity gains.
The Investor · Invest desk
Compiled by The InvestorSomething wrong?How this is made
A substitution trade only clears if the buyer can measure what the machine absorbed, and on Meta's own internal numbers the autonomous agents at the centre of Project OT were failing to deliver the productivity gains the plan had been built on [9]. So compare what shipped with what was scoped. A company-wide layoff of 10 per cent [8] against scenarios that took some teams down by as much as 60 per cent [4] is roughly a sixth of the ceiling, and the comparison is loose in Meta's favour, since one figure is company-wide and the other is team-level [1]. Against the cleaner yardstick, the roughly 25 per cent reduction an HR executive said Project OT would match or exceed [5], the delivered cut comes in at about 40 per cent of it [2]. The second wave never ran [7].
The more interesting term, or rather the one that runs the thesis backwards, is where the freed labour went. Meta says the exercise ultimately moved thousands of employees onto several newly established teams doing priority work [16], and it lists producing training data for its AI models among those priorities [12]. Headcount became an input to the models rather than a cost the models removed, which is a different business than the one the January retreat sketched, where virtual workers would be supervised by small talent-dense cadres of humans [3].
Three readings survive the evidence and they are not equally flattering: that agents cannot yet hold a job; that employees were in open revolt, convinced the AI programme was aimed at them [10], and a chief executive facing that does not need the technology to fail before he blinks; or that this was routine scenario planning that always contemplated redeployment as well as cuts [14]. Reuters, working from scores of internal documents and more than 20 people with knowledge of Meta's inner workings [18], could not determine what changed Zuckerberg's mind [17]. This is probably wrong, but I weight the first reading, for one procedural reason: Meta cancelled the November wave before it had determined how many people overall would lose their jobs [15], which is how a buyer behaves when he has stopped believing the delivery date, not when he is negotiating the size of the order. What would prove it wrong is a second wave reinstated under another name, or an internal agent-productivity series that turns, and the second would show up quietly well before the first.
Ranked by verification strength, evidence, and original report placement.
In January, Meta CEO Mark Zuckerberg and his top lieutenants gathered at his Hawaii compound for their annual leadership retreat and hatched a plan code-named Project OT, short for Organization Transformation.
The plan envisioned an "AI native" future for Meta in which AI would take over much of the daily work performed by thousands of human employees.
Virtual workers would be overseen inside Meta by smaller, "talent-dense" cadres of human staffers, according to one internal planning document reviewed by Reuters and three people familiar with the project.
In scenario-planning exercises, executives explored slashing the size of many teams across Meta by as much as 60 per cent, according to two people familiar with the project.
One human-resources executive projected the culling would be as big as or bigger than Meta's cuts of around 25 per cent three years ago, according to an internal document.
The restructuring was to be carried out in two waves, beginning with a first purge in May and followed by another shake-up in November, with layoffs supplemented by closing open positions and pushing out people Meta believed were poor performers.
Distinct publishers with included, body-backed reporting in this cluster.
1 article · September 2, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
leadership
Project OT put dates on the layoffs before it put numbers on the agents1 distinct publisher
product
Meta cancelled the AI plan that would have shrunk some teams by 60%1 distinct publisher
build
Meta dropped its November layoff wave before it ever set a headcount1 distinct publisher
product
Meta ran pods-plus-agents for a year and shelved it. Its own scoreboard says why1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Documents reviewed, not shown; company confirms the frame
The spine of this story is documentary — internal planning papers, posts and recordings, plus more than 20 people — and unusually, the subject confirms the contested parts on the record: Project OT existed, it had two waves, the worst scenarios reached 60 per cent for some teams. That combination is stronger than most exclusives get. What holds the score down is that readers see paraphrase rather than the documents, and the single most consequential claim — that the agents underperformed internally — carries no metric and no company response.
The org chart moved; the agents did not
Measured as work actually transferred to AI, adoption here is close to a null result — that is the story. One layoff wave ran, thousands of people were reassigned onto new teams including training-data work, and the November wave never left planning. Everything realised is a human reorganisation; nothing in this reporting shows agents holding production workload at scale, and Meta's plan to sell scheduling and sales agents to other companies appears only as intent.
Scenario documents read as strategy
The overstatement being documented is Meta's, and it is real: an 'AI native' company staffed by virtual workers and 'talent-dense' human cadres, scoped at up to 60 per cent of some teams, against agents that its own data said were falling short. But the telling adds a little of its own lift. A cancelled planning track and a scenario ceiling are treated with the weight of decisions, and the 10 per cent that actually happened sits next to a 60 per cent that was never a company-wide figure — a comparison that flatters the drama. Meta's line that it never assumed every scenario would proceed is self-serving and also, on this evidence, not refuted.
Leakers under threat, a company minimising, a wire in between
Read the interests in play. The people describing the scenarios are insiders in a workforce that believed it was being automated away — accurate and motivated are not exclusive, but the motive is plain. Meta's statement is drafted to shrink the story to a routine 'scenario planning exercise' that happily ended with thousands redeployed, and it declines to name the exempt units, which is precisely the detail that would let anyone size the plan. BNN Bloomberg is republishing wire copy with no stake of its own; Zuckerberg, the actor at the centre, was not made available.
Strong reporting, one pipeline
Confidence tracks the facts, not the narrative. The dated events and the two-wave structure are solid — a document for the May 19 cancellation, Meta's own confirmation of the shape of the plan. The causal story is softer: the reporting says plainly it could not determine what changed Zuckerberg's mind, so the agent data, the staff revolt and investor impatience sit as coincident pressures rather than proven cause. And every word of it reaches readers through one investigation carried by one publisher, with no independent newsroom to check the documents against.