Three clients, three design system conversations this year. All stuck in exactly the same place.

One building a system from scratch. One with a system nobody uses despite it being comprehensive. One where every product team quietly built its own version over three years.

All three, once I looked closely, were missing the same thing.

A design system is not a UI library. It is a decision-making protocol. It answers who can change a component, when, and with what alignment required. The components are just the artifact.

The client with the unused system does not have a documentation problem. Teams know how to use it and skip it anyway, because the system never told them what to do when a component does not serve the need. So they ship the workaround. That is the rational choice, not a rogue one.

Before you write another component spec, answer this: when two teams want the same component to behave differently, who actually decides? If nobody in the room can answer, that is the real project.

More on this in this week's issue of Design is Dead. Link in the comments.