Output was never the job

The layoffs that swept through tech design teams over the past year were not random. They followed a pattern, and the pattern says something uncomfortable about how design positioned itself during the expansion years.

Design headcount grew fast between 2019 and 2022. Ratios that had been one designer for every fifteen engineers moved toward one for every eight, sometimes one for every five. Companies were hiring designers the way they were hiring everyone else: because capital was cheap, growth was the mandate, and adding people felt like adding capacity.

But adding designers is not the same as adding design impact. And when the reckoning came, a lot of organisations looked at their design teams and could not clearly articulate what the return had been.

That is not entirely the designers' fault. But it is partly their problem.

The case I keep coming back to happened at a product company I worked with closely. When headcount pressure arrived, the design team braced for cuts. What they expected was a conversation about which designers to keep. What they got was a more uncomfortable question: what has this team actually changed?

Not what have they shipped. What have they changed. In the product. In the metrics. In the decisions that leadership made because design was in the room.

The team had produced good work. The screens were clean. The components were consistent. The user flows had been properly researched and tested. But when leadership looked for the thread between design activity and business outcomes, it was thin and hard to follow. Not because design hadn't contributed, but because design had never made the case for its own contribution in terms that the rest of the organisation was tracking.

Portfolios full of beautiful screens and no sentence about what changed because of them.

This is the credibility gap that has been building in the design profession for years. But the layoff wave has made it visible in a way that cannot be unseen.

Design earned its seat at the table during a period when "user-centred" was a differentiator. When companies could point to a beautifully designed product as proof of quality, and when quality correlated visibly with growth. In that environment, design's contribution was legible even without a business case. The product looked better. Users preferred it. Sales went up. The chain was loose but it held.

But that chain has been getting harder to see. As design standards rose across the industry, good UX became table stakes rather than competitive advantage. The companies that hadn't invested in design started catching up. The ones that had found themselves with large teams producing incremental improvements to products that were already well-designed.

The value of the work did not disappear. But the visibility of it did.

The designers who kept their seats, and kept their influence, were the ones who had already crossed a line that most of their colleagues hadn't crossed yet. They could translate design decisions into business outcomes. Not by learning to speak corporate. But by understanding what questions the business was actually asking, and answering those questions with design reasoning.

Not "we improved the onboarding flow." But "we reduced drop-off at step three by redesigning the permission request, which contributed to a 12-point lift in week-one retention."

Not "we simplified the dashboard." But "we reduced support tickets related to data interpretation by 30%, which freed up two support agents for higher-complexity issues."

The difference between those two statements is not the design work. It is the designer's decision about what the work is for.

Here is the uncomfortable part. The design profession has sometimes resisted this framing as a corruption of the craft. There is a version of the argument that says reducing design to business metrics misses the point of design: that good design serves people, not spreadsheets, and that the moment you start measuring design in revenue terms you have already lost something important.

I understand that argument. I have made a version of it myself.

But I no longer believe it holds as a complete position. Because the designers who frame their work only in craft terms are, in practice, dependent on someone else to make the business case for them. And that someone else is a leadership team that has competing priorities, incomplete information, and a budget to cut.

The designers who survive are not the ones who abandoned craft. They are the ones who understood that craft without legibility is a gift nobody can unwrap.

The layoffs were a correction. Not to design's importance. But to design's relationship with accountability.

The teams that come out of this period with more influence than they went in with will be the ones who made the translation. Who understood that sitting in the strategy room requires speaking the strategy room's language, not just showing up with better screens than anyone else.

Better screens are necessary. They are not sufficient.

They never were.