The quiet design revolution nobody is talking about.

Design has always promised us more than it delivers. Not out of malice — most designers I know are genuinely trying to make the world better, more legible, more human. But somewhere between intent and outcome, something gets lost. The gap between what we design and what actually changes in people's lives has never felt wider.

I've been thinking about this for a while, specifically since spending a year working on a product used by millions of people across the Global South. We obsessed over every tap target, every loading state, every moment of friction. The product shipped. Metrics improved. And yet, talking to real users six months later, the things they cared about had nothing to do with the interface we'd spent months perfecting.

There's a word I keep coming back to: legibility. Not in the typographic sense — in the sense that Scott uses in Seeing Like a State. Legibility is what happens when a complex system gets simplified enough for an outside authority to understand and manage it. It sounds good. It often looks good. But in the process of making something legible, you strip away a lot of what made it work.

Good design, in the current model, is essentially a legibility operation. We take messy human behaviour and render it into clean flows. We reduce ambiguity. We create structure. We make things measurable. And then we optimise against those measurements. The problem isn't that this doesn't work — it clearly does, in narrow ways. The problem is that we've confused legibility with improvement.

The alternative isn't less design. I don't think the answer is chaos or deliberately ugly things, though I understand the impulse behind that reaction. The answer is probably something closer to humility — a willingness to let the design recede, to let the people using it bring more of themselves to it.

I've started asking a different question when I start a project: not 'how do we design this better?' but 'what would it look like if we got out of the way?' Sometimes the answer is still a detailed, considered interface. Sometimes it's a much simpler artefact than we'd planned. Occasionally it's realising we don't need to build anything at all.

There are designers doing this well. They tend to work at the edges of what the industry considers design — in civic tech, in community tools, in open-source infrastructure. Their work rarely wins awards. It's hard to photograph. But it changes things.

The question I keep returning to isn't 'is design moving us forward?' — it's 'forward relative to what?' The metrics we use to measure progress were set by the people who benefit most from the current system. Engagement, retention, conversion. These are real things. They are not the only things.

Design is moving, constantly. It moves toward what can be measured, toward what can be shipped, toward what gets awarded and shared and talked about. Whether it's moving us forward — whether it's actually improving the texture of daily life for real people — that's a much harder question. One I'm not sure we're asking often enough.