A Layoff Labeled AI Owes the Team That Stays a Redesign.

On May 5, Coinbase announced it was cutting about 14% of its workforce, roughly 700 people. Its SEC filing gave two reasons, in this order: to "manage its operating expenses in response to current market conditions" and to "optimize the Company's operations for the AI era." The same day, Brian Armstrong sent a note to every employee and published it on the company blog. It names the same two forces, market first: "we're currently in a down market and need to adjust our cost structure now." Then AI: "I've watched engineers use AI to ship in days what used to take a team weeks."

Then the note does the thing a layoff announcement can skip: it tells everyone, including the people who stayed, how the company will work now. Five layers at most below the CEO and COO; no pure managers, with every leader required to "also be a strong and active individual contributor"; leaders who "will own much more, with as many as 15+ direct reports"; experiments with "one person teams." You can argue with that design, and I do. It is still a design: written down, sent to every employee the day of the cut, with a section addressed to "the team that is staying."

Now think about the last cut announcement your team read. If it said "AI" and stopped there, with no market, no plan, and no new shape for the work, the people who stayed did not receive an account; they received a headline. A team that has only the headline does not ask why the company cut. It asks whether its own work is next.

The conventional story makes the short version sound rational. AI makes some roles redundant, efficient companies trim to match, and the people who stay are told to upskill and prove they can work alongside the tools. The cut reads as discipline, and the burden of adapting lands on the employee.

AI has changed what some teams can deliver; Armstrong's note says so plainly. The smart companies, as I see it, redeploy that freed-up capability to dominate their market rather than cut headcount. A Harvard working paper by Fiona Chen and James Stratton, following 725,938 workers at 718 companies on one engineering-analytics platform through March 2026, found the extra code has not yet shown up as proportionally more delivered work. After their firms adopted AI agents, engineers wrote 30% more code, issues resolved showed no measurable gain, and the time from pull request to merge rose 49%. The paper also ruled out overall employment declines larger than 2.9% at those firms.

An announcement that says "AI" and shows no redesign is an easy way to pass off a failure in planning or in the read of the market. Naming either means owning it. The label implies the work left with the people, and that implication is the expensive part, because it gives no one a reason to re-derive the Design Load of the seats that remain. Design Load is my term for what a specific seat actually demands, derived again for the work in front of it. Without that step, the job descriptions stay as written, and the work lands on whoever is still there.

The team fills the silence with its own story, and the AI label makes that story specific: my work is next. The team members with the most skill, especially the most judgment, quietly update their resumes and start looking. The people without real options try to become indispensable, and the load they take on can run past what they can carry.

All of us in this industry with significant experience have seen what happens next, and I have been through repeated booms and busts in a career of more than thirty years. Some people burn out and leave anyway; some make mistakes in work outside their depth; some become the single point everything waits on. The outcomes differ, and underneath each one I see the same thing: the load was redistributed and never redesigned.

That is Coordination Debt: coordination capacity removed without redesigning where its work goes. Coinbase removed layers too, and it published the new shape the same day; that is the account its people were owed. Even so, I believe Coinbase will eventually run into Coordination Debt with what it did. As I wrote on October 13, "it is as you head toward fifteen that it gets unwieldy," and this design allows fifteen-plus. Coordination Debt compounds quietly while the work still ships, until the slowdown arrives and reads as proof the company needs more AI or a leaner team.

Breaking this loop takes refusing to let someone else's sentence explain your team's situation. When a cut lands on your team, your job is to cut through the noise: help the team understand what really happened, and move forward with accurate thinking.

Name what changed, whether the market, the plan, or the work AI actually absorbed. Re-derive the Design Load of every seat that remains, with the people sitting in them. If AI freed capacity, say where it is going. Either you supply the account, or the headline does.

This week, ask someone on your team who was not in the room why the last cut happened. If the answer is "AI," and you know the real reason was something else, the label is running your team. You are the one who tells them what the work looks like now.

I send a short daily email on exactly this kind of thing; today's was about re-deriving the Design Load of every seat a cut leaves behind. Get the next one here: https://technicalleader.coach/daily-email