Your Design System Is Not the Product

Six months in, the system is beautiful. Every token is named. The documentation site has a search. And the product has shipped nothing that a customer noticed.

I have been on both sides of this, and it is always the same story told with different component names.

How It Goes Wrong

• The system gets a roadmap. The moment it has its own quarterly goals, it stops serving the product and starts competing with it.
• Coverage becomes the metric. Ninety-four components, of which the app uses eleven.
• Nobody is allowed to break it. A system that cannot be violated under deadline is a system teams will route around.

A design system earns its cost in the second year. If it has not paid for itself by then, it was a hobby.

What A Healthy One Looks Like

It is smaller than you want. It documents decisions rather than options. It has an obvious escape hatch, and the escape hatch is used a few times a quarter without anyone filing an incident.

Most importantly, someone can tell you which shipped feature was faster because of it. If nobody can, the system is not the product and it is not helping the product either.

Build the third version of a component, not the first. The first two teach you what it actually needs to do.