Meta's flattening has a due date: late April for tech, late May for business

The order of operations is the argument. Recruiting goes first and is told within a day ^[6], the only part of the plan that lands faster than it was announced, because a company that has decided to reduce its hiring rate has already decided what to do with the people who hire ^[2]. Everything after that runs on a slower clock, and it has to: flattening and project cancellation are one decision taken twice, since you cannot remove a management layer until you know which work under it is going away ^[2].

Then the arithmetic. Around 10,000 people leave and around 5,000 approved-but-unfilled roles are closed ^[5], so the reduction against plan is 15,000 positions, a third of which never had anyone in them ^[13]. That third is the cheap third. It carries no severance and no announcement date. The 10,000 is what the two named months are for ^[3].

The reason given for publishing dates at all is that the prospect of org changes creates uncertainty and stress, and that Zuckerberg wanted the company past it early in the year ^[8]. The memo then schedules that uncertainty rather than ending it: tech in late April, business a month later ^[3], separate timing for international teams whose local leaders will follow up ^[10], and a small number of cases running through the end of the year ^[4]. For anyone in that tail, the wait is roughly nine months from the memo ^[15]. Whatever that is, it is not the early resolution the same paragraph promises ^[8].

The detail worth copying is the one that costs nothing to disclose and reveals the most: hiring and transfer freezes lift group by group, after each group's restructuring ^[7]. Between the memo and their date, employees who suspect their own work is one of the lower priority projects ^[2] cannot move to a team that will survive, because the freeze is still on. The company holds its options on who to cut for two more months. The individual holds none until the cut has happened.

The stated logic for the layer removal is that every level of hierarchy adds latency and risk aversion to decisions, and that managers polish work on its way up the chain ^[9]. That is a durable argument and it long predates this memo. What is new here is that it comes with a delivery week, alongside a separate summer deadline for the hybrid work analysis ^[12]. A date is the only part of a restructuring announcement that the people it happens to can audit. In late April and late May, Meta's own staff get to see which leaders shipped what the memo committed them to.