Every few months someone declares a design tool dead. Figma is dead. Wireframing is dead. The design file is dead. Design systems are dead. User research is dead, again.
None of them have died. What has happened is worse than that: nothing has replaced anything. Design tooling has stopped existing on a single and predictable path and has started scattering. A designer might sketch in one tool, prompt in another, build in a third, review in a fourth and keep the real thinking in a notes app. The next designer along will do it in a different order with different tools. Design used to have a canonical stack. That's the thing that died.
The usual explanation is that the new tools are better than what went before. Some are. The larger driver of the scattering is that most of them are hard to use and nearly impossible to discover, to an extent which would have embarrassed us all five years ago. Capabilities hide behind prompts. Features are released without being announced and change without being documented. The interface is a text box and an expectation that you will work out what it can do. So designers don't adopt a tool, they assemble one. Each person keeps the pieces that worked for them and drops the ones that didn't, and the result is a toolchain for one, multiplied by the number of people doing the work.
This is a problem for leaders. We have spent years standardising tools because standardisation was how we got consistency. Same file, same library, same review ritual. If the tools now differ designer to designer, that route is closed. You can mandate a tool, but you can't mandate how someone actually works, and the people with the strongest instincts will route around you first, especially when doing so gives them the feeling of being more efficient.
So consistency has to come from somewhere else. It has to come from underneath the tools.
This is where design as infrastructure stops being a slogan and becomes a requirement. If the tool can't communicate a standard, the standard has to be reachable from any tool. That means the context a designer needs, the system they build within and the operating model that says how decisions get made all have to exist at a level of abstraction that a sketching tool, a prompting tool and a coding agent can each read. Tokens and components are the easy part. The harder work is the layer above: why we make the choices we make, what the product is for, what it should never feel like. Right now that lives in people's heads and in documents nobody opens.
I've made the point before that AI is the primary future customer of the design system. I want to extend that. The customer is any tool a designer picks up, and there are going to be hundreds of them. A system that can only be consumed through one interface is a system with one customer, and that customer won't last long, either.
This chaos must not reach the work we ship. What customers see has to feel like one thing, built by one organisation with one point of view, even though it was assembled by a hundred people using a hundred different workflows. The software landscape producing it will be incoherent. The output can't be.
That is the job now. The tool wars were always a distraction, and the new fragmentation makes them irrelevant. The teams that do great design work will be the ones whose context is legible to every tool they pick up, including the ones that haven't launched yet