Design systems die when they are somebody else's job
Three of our clients now run their own design systems. The two that stuck had one thing in common, and it was not the documentation.
Aye Chan Moe
Head of Design
We have built design systems for six clients. Three are alive and being extended by their own teams two years later. Three quietly rotted into a Figma file nobody opens and a component library everyone works around.
The difference was not documentation quality. Two of the dead ones had better documentation than the living ones.
What actually predicted survival
Someone whose job it is. Not "a designer who also maintains the system" — a named owner with allocated time. The systems that died all had a system that was everybody's responsibility, which means nobody's.
It was faster than not using it. If a designer can build a screen quicker by ignoring the system, they will, and they should. Every dead system had gaps that made the shortcut rational. The living ones covered the boring 90% so well that reaching outside it felt like extra work.
It shipped incomplete. The systems that died were built comprehensively, launched at v1.0, and were immediately wrong about a dozen things nobody could correct because it was Finished. The ones that lived shipped with twelve components and a clear way to add the thirteenth.
What we build now
Tokens first, components second. Colour, spacing, typography, radius, motion — as tokens, in code, generated from one source into CSS variables and platform equivalents. Get this right and components are easy. Get it wrong and every component encodes the mistake.
Accessibility in the token layer. Contrast pairs are defined as pairs. You cannot pick a foreground that fails against its background because the token *is* the pair. This removes the entire category of "we will do an accessibility pass later", which is a pass that never happens.
A contribution path on day one. Not a governance document — an actual, tested route: here is the branch, here is the review, here is who says yes. If contributing is undefined, the system stops growing the moment we leave.
Motion as tokens too. Durations and easing curves, named. Otherwise every engineer picks their own and the product feels like six products.
The handover that works
We do not hand over a finished system. We hand over an unfinished one, plus two weeks where their team adds the next four components while we are still in the room to be asked stupid questions.
The systems that survived were the ones where the client's team had already shipped something into it before we left. Ownership is not transferred in a document. It is transferred by doing the work once with someone watching.
