“We don’t have the states designed.” A developer on a team I worked in told me that about a component whose states were all designed and sitting in the library. I sent the link, they found what they needed, and a week later the same question came back about a different component, so I sent another link. After a few rounds of this, a good part of my week was going into being a search engine for a library that already had the answers in it.
When I’ve asked for time to document a system properly, the answer has usually been “we don’t have the time”, which is a fair answer for the week it’s given in. It also decides who pays later, and that tends to be the designer, one question at a time. The times I did document everything, the documentation mostly went unread, and the questions kept coming anyway.
The system was adopted where someone had the job of looking at it
Once, on a bank’s design system that ran across several countries, we had the time to do it properly. We documented the work, sent a newsletter to the designers explaining what was changing and why, and worked with one named person in each country who was in charge of leading their teams towards the system. The team that ended up adopting the foundations we built, without anyone telling them to, was the global design system team. Their job was to look at systems, so they noticed what we were doing and started merging the two into one.
Everywhere else, an update lands as a change nobody had time to understand
The merge reached everyone else as a library update. The information was shared and everyone was expected to use the new components, but the designers doing the daily work weren’t given the time to understand why things had changed, to question it, or to think about what it meant for their own screens.
Picture what that does to a designer in the middle of a project. They update the library, and the buttons on the screens they’re working on change. The screens from their earlier projects don’t, because nobody is going back to those, and several development teams are building from both versions at once. Nobody decided to leave the older screens behind and nobody owns finishing them, so that work never ends. That’s Drift, which is what happens in the absence of a decision.
I’d expect any company in that position to keep presenting its design system with a straight face, and in the presentation the claim holds. The product says something else, one screen at a time, and that distance between what a company says it is and what it hands a person to use is Said and Shipped.
An owner with a second job is a name on a slide
The named owner in each country was the part I’d have bet on. Each of them was also busy with their own work, so the system arrived as a second job they had been handed and hadn’t chosen. The newsletter got a similar reception from a lot of the designers it was written for. They had their own projects to deliver, and nothing in their week made room for the system.
How much time an owner gets is a decision, and at a startup I’d expect it to be the founder’s. Documentation, training and a named owner all depend on it, because each of them needs someone with hours in the week to keep it going.
At twelve people, the old version gets copied instead of left behind
A twelve-person company has fewer teams and fewer screens, and the same condition: a product that keeps shipping while the system under it changes. What has moved since that project is where the product gets made. From what I see, a lot of small teams now use the design file as the starting point and build the rest straight into the code, often with AI doing a good part of the implementing.
That moves the old version from a file nobody opens to the product itself, where it doesn’t stay put. I’d expect an agent asked to build the next screen to copy whatever it finds in the codebase, old components included, so every week nobody moves them, there are a few more of them. And at that size the person who would own the system is likely to be the same person shipping the next feature, so the second job arrives on day one.
After every change to the system, look for the old version
After the next change to your system, ask whoever builds the product to search for what was replaced, the old component or the old colour value, and list where it still shows up and who is moving each one. If the list has places and no names, you’ve found where your system stops.
That’s also where Hold ends. Its last week sets up how the system gets owned, how people contribute to it and how design and development stay in sync. The hours that ownership needs come from your side, so they’re one of the first things we ask about on an intro call.
