buildConfirmed4 publishers Project OT would have cut some teams by 60 percent. Meta's own numbers showed incidents up 40 percent and the time spent on them up 70, and Zuckerberg killed the second wave.
Perspective Coverage
4 publishers
- Builder
- Builder 27%
- Operator
- Operator 49%
- Investor
- Investor 24%
Reality
- Evidence60
- Adoption45
- Hype gap+25
- Incentives50
- Confidence58
Project OT sketched an AI-native Meta with much smaller teams and fewer management layers, and Zuckerberg has been using a CEO agent to skip several of them. The internal coding numbers did not follow.
Reality
- Evidence27
- Adoption20
- Hype gap+38
- Incentives62
- Confidence33
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.
Reality
- Evidence76
- Adoption54
- Hype gap+28
- Incentives62
- Confidence70
buildOne report1 publisher Reuters reports that Meta's OT plan modelled cutting some teams by 60 percent and putting small human crews over agent workflows, while internal indicators said the agents were not delivering the productivity the plan assumed.
Reality
- Evidence48
- Adoption42
- Hype gap+28
- Incentives66
- Confidence46
Reuters reporting on Project OT, relayed by the Pragmatic Engineer, shows Meta's reduction target was fixed in January while the productivity claim underneath it was still untested in May, and half the plan ran anyway.
Reality
- Evidence52
- Adoption45
- Hype gap+30
- Incentives58
- Confidence50
buildOne report1 publisher The plan assumed smaller teams would work as well as before, which is a bet on 2.5 times the output per head. The version that actually shipped, a 10% layoff plus infra engineers seconded to labeling, left outages behind.
Reality
- Evidence55
- Adoption35
- Hype gap+15
- Incentives60
- Confidence52
buildOne report1 publisher Project OT put individual teams in line for cuts of up to 60% on the assumption that agents would absorb the work. By May the internal productivity read had turned. The second wave never got a total.
Reality
- Evidence58
- Adoption62
- Hype gap+30
- Incentives68
- Confidence55
Meta's own telemetry showed its agents producing far more internal churn than shipped features, plus more incidents to clean up. That is the strongest evidence yet that agent programmes do not cash out as headcount.
Reality
- Evidence72
- Adoption64
- Hype gap+18
- Incentives68
- Confidence61
Sam Altman says AI adoption is slower than he expected. Meta has dropped a plan to cut some teams by up to 60 percent. In both accounts, the scarce resource is people who can map real work onto what agents can actually do.
Reality
- Evidence31
- Adoption37
- Hype gap+14
- Incentives61
- Confidence36
The exits and the transfers landed together: a capital budget of $125bn to $145bn is being staffed off the existing payroll. The Project OT documents show how much further leadership was prepared to go.
Reality
- Evidence22
- Adoption38
- Hype gap+30
- Incentives65
- Confidence25
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.
Publishers:tbsnews.net
Reality
- Evidence58
- Adoption34
- Hype gap+46
- Incentives71
- Confidence55
Internal telemetry reported by Reuters shows code changes up 220% while user-facing changes rose 36%, and major incidents up 40%. The cuts of up to 60% did not happen.
Reality
- Evidence52
- Adoption61
- Hype gap+44
- Incentives66
- Confidence54
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.
Reality
- Evidence44
- Adoption33
- Hype gap+41
- Incentives61
- Confidence46