The Chart and the Layoff, Same Week

On July 6, Xbox CEO Asha Sharma emailed her division what she called the most significant restructuring in its history. "Our business today is not healthy," she wrote. "We simply spread ourselves too thin." Thirty-two hundred jobs cut, twenty percent of the division, sixteen hundred of them immediate. Four studios spun out.

The memo was unusually candid for the genre. Sharma didn't hide behind vague language about strategic realignment. She said plainly which specific bets hadn't worked. Game Pass grew, just not fast enough. The multi-platform push underdelivered. The studio acquisitions never paid off. Xbox margins, she said, run three to ten times lower than comparable platform and publishing businesses. Most executives don't hand employees that much of the real picture on their way through a restructuring.

What she didn't hand them was an apology.

Forbes columnist Kevin Kruse pointed out the pattern this cut belongs to: leaders standing next to a chart celebrating automation gains the same week people lose their jobs to that automation, math intact, empathy nowhere. Microsoft didn't need a literal chart for the point to land. The company's public story that week was still record AI infrastructure spending and accelerating cloud growth, the same story it had been telling all year. Xbox was the unit absorbing those costs, and the people receiving that memo knew it.

Perhaps that omission was cruelty. Or it was simply a sequencing choice, and sequencing choices are design choices whether anyone treats them that way or not. Someone decided the AI narrative belonged to one channel and the layoffs belonged to another, and nobody asked whether the two could be said in the same week to the same audience without one of them swallowing the other.

It can't be done cleanly. Not because employees are unreasonable, but because when the wins get celebrated in the same channel as the losses are announced, employees have to hold both at once, and they will always notice which one the company chose to lead with.

---

The Order Problem

There's a simple order most of these announcements get backward. Acknowledge the cost first. Then lay out the concrete support: severance, transition help, whatever actually exists. Only then make the business case.

Sharma's memo was heavy on the third step and thin on the first. That's not unusual. Skipping the business rationale would cost a company nothing. Skipping the acknowledgment is what costs something, because acknowledgment means admitting in public that the tradeoff was real and someone made it. That's a harder sentence to write than a margin comparison.

Microsoft isn't alone in this. GM ran scripted, impersonal layoff meetings this year and got the same backlash. CEO empathy ratings have been sliding across the board, and the common thread isn't a shortage of emotional intelligence. It's an ordering habit. Justification comes first because it's safe. It has a slide and a number attached to it. Grief doesn't have either, so it gets said last, if it gets said at all, and the order becomes the real message whether or not anyone chose it deliberately.

---

The Design Flaw Worth Naming

Companies build entire departments, comms, legal, PR, to make sure a message survives contact with the public. Almost none of that machinery is pointed at a much smaller question: in what order are we saying these two true things, and what does the order itself tell people?

A memo can be completely accurate and still fail as governance, if the sequence it follows quietly tells employees which one mattered more.

Ethics by design means treating the order of a message with the same seriousness as its content. Not as a soft skill layered on top of a hard decision, but as a decision in its own right, made by somebody, reviewed by nobody, felt by everybody on the other end of it. If the AI wins and the layoffs have to land the same week, the least a company can do is know on purpose which one goes first, and be able to explain why.

Maysa Hawwash, Founder and CEO, ScaleX