Leadership1 distinct publisher3 min readPublished
Meta worked backwards from a 60% team-cut scenario to a May and November schedule, then cancelled one wave hours before the first. The design failed ahead of the technology, and the ordering is the lesson.
The Board Room · Leadership desk
Compiled by The Board RoomSomething wrong?How this is made
The dependency chain ran backwards. A 60% reduction in a team's size is not a claim about a model, it is a claim about span of control: that one remaining human can supervise enough virtual work to cover the output of the colleagues who left [2]. That claim is testable, but only one way, by running it on a few teams and measuring what comes out the other end. Project OT fixed the calendar first, a May purge and a November shake-up, and left the measurement to catch up [4].
It did not catch up in time. Roughly four months separate the January retreat from the reversal on the night of 19 May [1]. Inside that window, internal data indicated the autonomous agent technology at the centre of the strategy was not delivering the productivity gains the plan assumed [7]. Two other pressures were live at the same time: employees had concluded the AI transformation was partly aimed at replacing them [6], and some investors were asking what Meta had to show for its AI spending [8].
A skeptic would say Meta got what it wanted regardless. It cut 10% of staff on 20 May [5], and it says the exercise moved thousands of employees onto newly established priority teams [12]. That is fair, and it is also the diagnostic. Redeployment and open-role closures need no agent autonomy at all; the part that was cancelled is the part that depended on virtual workers doing the work of departed staff.
What the record does not support is a verdict on model capability. Reuters reported it could not determine what prompted Zuckerberg to change course, or what Meta's current workforce plans are [13]. Meta's own account is that scenario planning is not commitment, that it never intended to lay off 60% of its workforce, and that leaders killed the second wave before anyone had settled on a total number of job losses [11]. Read the sequence, not the technology: the company committed to two dated waves before it held evidence that the substitution worked, and the second date was the one it could still take back.
The gap between the projection and the outcome is the size of the retreat. One HR executive had the culling landing at or above Meta's roughly 25% reduction of three years ago [3]; what actually shipped was 10%, about two-fifths of that benchmark [2]. The cost of the exercise sits in what it taught the workforce. Any team at Meta now offered an agent as leverage has already been shown a planning document in which agents were the argument for cutting the team [1], and the next attempt at this pays that price before it starts.
Ranked by verification strength, evidence, and original report placement.
Project OT, short for Organization Transformation, was conceived at Zuckerberg's annual leadership retreat at his Hawaii compound in January; the plan envisioned an "AI native" Meta in which AI took over much of the daily work of thousands of human employees, with virtual workers overseen 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%, with some employees offered roles in new units and others laid off, according to two people familiar with the project.
Meta acknowledged the plan was to be carried out in two waves and that the most drastic scenarios involved reducing the size of some of its teams by up to 60%, but declined to specify which units were involved and said several major ones were not part of it.
Meta said the scenarios included both layoffs and redeployments, that the company at no point intended to lay off 60% of its entire workforce, and that leaders cancelled plans for the second wave before determining how many people overall would lose their jobs.
One Meta human-resources executive projected the culling would be as big as or bigger than the company's cuts of around 25% three years ago, according to an internal document.
Internal planning documents showed the restructuring would run in two waves, a first purge in May 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.
Follow any of these and your For You feed starts watching them — no settings page required.
product
Meta's 60% agent conversion, and the supervision ratio nobody published1 distinct publisher
product
Meta ran pods-plus-agents for a year and shelved it. Its own scoreboard says why1 distinct publisher
science
Meta counted the code its agents wrote, then cancelled the layoffs1 distinct publisher
product
A satirical scoreboard counts 17 agent escapes that hacked somebody else's company1 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.
Documented structure, unmeasured mechanism
The structural spine - Project OT's existence, the 60% team-cut scenarios, the two-wave May/November schedule, the reversal and the 10% layoff - rests on internal documents plus more than 20 sources and is confirmed on the record by Meta, which is strong for a leak-based story. But the causal mechanism the story turns on (agents failing to deliver productivity gains) and the investor-pressure strand carry no metrics, names, or figures, and Reuters concedes it could not determine what triggered the reversal.
Restructuring shipped, agent substitution did not
Real organizational change was executed and disclosed: a 10% layoff wave and thousands of employees redeployed onto newly established priority teams including AI training-data work. The AI-native substitution that justified the plan was not adopted at scale - the November wave was cancelled, the 60% scenarios were not carried through, and no deployed agent workload or productivity outcome is documented.
Plan outran its evidence
Positive gap: the AI-native thesis inside Meta was operationalized into dates and 60% team-cut scenarios before any documented productivity result from agents existed, and the story's own framing of AI replacing thousands of workers exceeds what the disclosed evidence and the executed outcome support. The gap is moderate rather than extreme because Meta confirmed the plan's structure on the record and real cuts and redeployments did occur, and because the article itself reports the unravelling rather than amplifying the promise.
Strong incentives on both the corporate and source sides
Meta has a clear interest in reframing a scrapped mass-automation plan as routine cost cutting and redeployment - it confirmed the skeleton while declining to name affected units, refusing a Zuckerberg interview, and stressing that scenarios were 'never assumed' to all proceed. On the other side, the account rests on anonymous insiders and leaked documents produced during a period of open employee revolt, where sources have their own stake in how the plan is characterized, and the outlet carries a high-profile investigative scoop.
Solid on facts, single-channel on interpretation
Confidence is supported by an on-record corporate confirmation of the plan's structure and by a broad documentary base, but constrained by there being exactly one publisher item in the cluster, by anonymity of the human sourcing, by the absence of any quantified agent or financial data, and by the explicitly unresolved cause of the reversal.