Name the number, the reason, and the effective date in the first two sentences, tell employees before the public finds out, and make sure the explanation you give actually matches how the news was delivered. Most layoff announcements fail on the third point, not the first two. A company can disclose a clean number and a plausible reason and still turn the story into a scandal, because reporters and former employees compare the stated reason against the method of delivery, and a mismatch between the two is what actually goes viral, not the layoff itself.
What does a layoff announcement actually have to say?
Four things, stated plainly and in order: how many people, what share of the workforce, why now, and what departing employees receive.
Vague language in any of those four spots reads as evasive within hours, not weeks. "Streamlining the organization" or "aligning with strategic priorities" are the two phrases almost every weak announcement reaches for, and they read exactly the same whether the real reason is a demand slowdown, a merger, or a shift toward AI tooling. A specific reason, even an uncomfortable one, holds up better than a vague one, because a reporter who cannot get a straight answer from the release will go find one from a laid-off employee on social media instead, and that version of the story is rarely the company's.
What happens when the delivery method contradicts the message?
It becomes the story, and the stated reason stops mattering.
The clearest case is Better.com, where CEO Vishal Garg laid off roughly 900 employees in December 2021 on a single Zoom call, telling them directly, "If you're on this call, you are part of the unlucky group that is being laid off," and "Your employment here is terminated effective immediately." Multiple outlets reported that Garg cited the market, performance, and productivity as reasons, which might have been defensible reasons on their own. They were never discussed, because the format of the call, three minutes, no names used individually, delivered days before the holidays, became the entire news cycle. Garg apologized days later in a leaked internal letter, writing that he had "blundered the execution." Better.com's VP of communications, its head of PR, and its head of marketing all resigned in the aftermath. The lesson is not that the layoff itself was indefensible. It is that no stated reason survives a delivery method that looks cruel on video.
What does a well-handled layoff announcement look like?
Brian Chesky's May 2020 memo to Airbnb staff is still the example most comms teams point to, and the reasons are specific, not vague.
The memo, published on Airbnb's own newsroom the same day employees were told, opens with Chesky noting it was his "seventh time talking to you from my house," a small detail that signals this was one update in an ongoing relationship with staff, not a single abrupt event. The core number comes in the second paragraph, stated without hedging: "Out of our 7,500 Airbnb employees, nearly 1,900 teammates will have to leave Airbnb, comprising around 25% of our company." Severance terms follow immediately and specifically: US employees would receive "14 weeks of base pay, plus one additional week for every year at Airbnb," with at least 14 weeks guaranteed everywhere else, plus 12 months of healthcare coverage. Chesky also addressed the selection logic directly, writing that cuts were "mapped to a more focused business" and that the decisions were "not a reflection of the work from people on these teams," language that answers the question every remaining and departing employee is actually asking: was this about me, or about the business.
Source: Cloudflare's Form 8-K filed with the SEC on May 7, 2026, linked in the article.
What changed in 2026, when AI became the stated reason?
The reason got easier to state and harder to reconcile with the company's own results.
Cloudflare's May 2026 restructuring is the clearest version of this pattern. The company's own Form 8-K, filed with the SEC on May 7, 2026, states that Cloudflare would "reduce its current workforce by approximately 20%" as part of a plan "designed to further accelerate its evolution to an agentic AI-first operating model." The filing puts total restructuring charges at $140 million to $150 million, split between $105 million to $110 million in cash, covering "notice periods, severance payments, employee benefits and related costs," and $35 million to $40 million in non-cash charges tied to vesting of share-based awards. The cuts were announced alongside first-quarter results showing revenue of $639.8 million, up 34% year over year, which is the detail that drew the most criticism: a company citing AI efficiency gains while posting record growth has to work harder to explain why the two facts sit in the same release. Cloudflare's answer was to be specific about which roles were affected. In a Wall Street Journal op-ed days later, CEO Matthew Prince wrote that "the vast majority of those we laid off last week were measurers," meaning middle management, finance, legal, and internal audit roles, rather than the engineers building the product. That specificity, naming the function rather than leaving readers to guess, did more to contain the story than the AI framing did on its own.
Should employees or the public hear first?
Employees, always, and with enough runway that nobody reads about their own job loss before they have been told directly.
A CEO transition announcement can sometimes work on a public timeline first, because the people most affected, investors and the board, are usually part of the decision already. A layoff is different. The people most affected learn about it last if the sequence breaks, and a leak to the press before an internal meeting is the fastest way to turn a hard but manageable announcement into a story about how badly the company handled its own employees. Where a public company's disclosure obligations require a filing before every employee can be told individually, as is often the case for a workforce reduction material enough to need an 8-K, the internal all-hands briefing and the public filing should land within hours of each other, not days.
What should never go in a layoff announcement?
A reason that doesn't survive a follow-up question, and a tone that doesn't match the news.
If the honest reason is financial distress, say so; euphemizing it as "strategic realignment" when a reporter can check the balance sheet only invites a worse story once the gap is noticed. If severance, healthcare continuation, and outplacement support exist, state the specifics in the same release rather than promising "generous support" without numbers, because vague generosity reads as no generosity at all once someone asks a former employee what they actually received. And if the situation is contested enough that the stated reason might not hold up to scrutiny, a crisis communication plan, not a standard layoff template, is the right starting point, because the standard four-part structure assumes the facts are stable enough to state plainly.
How does this fit into the company's broader reputation?
A layoff announcement is rarely read in isolation. It gets read against the company's last earnings call, its last hiring announcement, and whatever reputation it already has with the press. A company with a consistent record of plain, specific communication gets a more forgiving read on a hard announcement than one that has previously overstated its numbers or dodged direct questions. That is one more reason a layoff announcement should not be improvised in isolation; it is one more data point in whatever PR strategy the company has been running all along, and it will be judged against that record, not against the announcement alone.
The direct answer, for anyone who read this far
State the number, the share of the workforce, the real reason, and the severance terms in the first two sentences, tell employees before anyone else, and make sure the delivery method does not contradict the explanation. Talk to White Ocean Media if a workforce reduction is coming and the announcement needs to hold up under the follow-up questions it will get within hours.
