Skip to content

ProductNot yet confirmed elsewhere1 publisher3 min readPublished

Meta ran pods-plus-agents for a year and shelved it. Its own scoreboard says why

Reuters says Project OT scoped some teams for cuts of up to 60 percent. Meta's internal data showed code changes up 220 percent and features reaching users up 36.

The Product Desk

How we use AISend a correction

Photograph accompanying Meta ran pods-plus-agents for a year and shelved it. Its own scoreboard says why
Photo: bnnbloomberg.ca

What happened

  • Reuters reports Meta spent much of this year testing Project OT, a plan for AI to take over many of the workforce's daily tasks.
  • Executives considered cutting some teams' headcount by as much as 60 percent, part layoffs and part unfilled roles and managed exits.
  • Zuckerberg dropped or paused the November layoff wave, and Meta now describes the deeper cuts as scenarios under consideration.

Why it matters

  • cost The keystroke and mouse-movement collection bought training data for agents that were then paused, and the bill was 19 points of employee sentiment plus fresh organising energy that does not unwind.
  • precedent Anyone selling small-pod-plus-agent org charts now has to answer a company with its own models and its own measurement that tried it for a year and stopped.
  • exposure Staff got a calendar-bounded assurance, not a repudiation, so the plan's premise carries into 2027 while the evidence that failed it stays inside the company.
  • contradiction Meta calls the 60 percent scenarios hypothetical, but an HR executive was already sizing cuts against 2023's 25 percent, and how far the plan really got changes what the pause means.

The useful artifact here is not the cancelled layoff wave. It is the scoreboard Meta seems to have kept while the experiment ran.

Code changes to the company's AI software platforms and infrastructure were up 220 percent year over year [9]. New or improved features that actually reached users rose 36 percent [10]. Technical and security incidents rose 40 percent, and the hours employees spent dealing with them grew 70 percent [11][12]. Set the first figure against the second and the activity-to-delivery ratio is roughly six to one [20]. Set the incident-time figure against delivered features and the cleanup grew close to twice as fast as the work that reached users [21].

That is the arithmetic a chief executive has to look at when the reorganisation on the table assumes the opposite. The design laid out at January's leadership retreat had agents overseen by smaller human pods, with engineers, designers and product managers moving into general-purpose "builder" roles and agent-assisted analysis helping set daily priorities [5][6]. Executives had been watching startups, some of them in Asia, built that way [19]. The premise is that supervision can thin out while output thickens. Meta's own incident-time number points the other way: whatever the pipeline was producing needed more human attention after it shipped, not less.

Two caveats worth keeping. The figures are internal, reported at second hand through Reuters, and the account does not say the incidents were caused by agent-written work [1]. Nor does it define an incident or give a baseline. What it does establish is that the people holding the numbers read them as thin enough to stop on. In July, Zuckerberg told a town hall he had overestimated the pace, saying the "trajectory of the agentic development over at least the last four months hasn't really accelerated in the way that we expected" and that the agent investment had not "come to fruition yet" [13].

The sequencing is the part other operators should sit with. Meta installed software on US employees' computers to capture mouse movements and keystrokes, training data for the agents meant to replace them [14]. Complaints flooded the internal network, employee sentiment scores fell 19 points, and organising activity grew [15]. The collection ran ahead of any evidence the agents would clear the bar. The sentiment was spent; the agents were paused [3].

None of which retires the idea. Reuters reports the broader plan is not necessarily dead, and Zuckerberg's reassurance covered company-wide cuts "this year", leaving staff worried about smaller reductions now or larger ones in 2027 [16]. Smaller AI-assisted teams are still running in parts of the company, capital expenditure on AI infrastructure continues, and investors are still waiting to see returns attached to it [17]. The experiment failed its own test once. The pressure that produced it did not go away.

What to watch

  • Whether any Project OT measurement is published with baselines and a definition of "incident", which would let the activity-to-delivery gap be checked rather than inferred.
  • Whether the plan returns in 2027, given that the assurance to staff covered company-wide cuts for this year only.
  • Whether the keystroke and mouse-tracking program keeps running now that the agents it was feeding are paused, and what the organising activity does next.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence44
Adoption33
Hype gap+41
Incentives61
Confidence46
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Reuters reports that Meta spent much of this year testing a plan, dubbed Project OT, in which AI would take over many of the workforce's daily tasks.

    ReportedSupportedSource: Reuters, via Engadget2 sources— create a free account to open themView cited source
  2. [2]

    Project OT is short for "Organization Transformation", and in its original form reportedly included a second wave of layoffs in November.

  3. [3]

    Zuckerberg ultimately abandoned or at least paused the November layoff wave, for reasons Reuters did not uncover.

Sources

1 independent publisher whose own reporting we read for this story.

  1. engadget.com

    2 articles · August 26, 2026

    Meta reportedly abandoned an AI-focused restructuring plan that would have laid off thousands

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Topics

Loading related stories