The documentation nobody opens

Many teams have a design system. Far fewer teams use it. I have seen beautiful libraries with hundreds of components that designers ignore because it is faster to draw a new button than to find the right one. A design system is only valuable if it makes daily work easier.

On a recent freelance project, I built and maintained a Figma system of around 60 components. After a few months, designing a new screen took roughly 20% less time. Here is what made the difference.

1. Start from real screens, not theory

I did not start with a list of "all components a product might need". I started with the screens we already had and collected what repeated: buttons, inputs, list items, cards, sheets. If something appeared only once, it did not go into the system yet.

2. Tokens first

Colours, type sizes, spacing and radius were defined as tokens before any components. This sounds boring, but it is the reason the system stayed consistent. When we changed the brand colour, we changed one token, not 200 layers.

3. Fewer components, smarter variants

Instead of five different card components, we had one card with clear variants and properties. Auto Layout did the hard work, so the same component worked with short text, long text and different screen sizes. Fewer components means less searching.

4. Names people understand

"Button / Primary / Large" is better than a clever internal name. I named everything in the language the team already used in meetings. If a developer and a designer both understand the name, the system is doing its job.

5. Documentation inside the file

Nobody reads a separate 40-page document. Short notes next to each component (when to use it, when not to, one good and one bad example) were enough. The rule: if it does not fit next to the component, it is too long.

6. Treat it like a product

A design system has users: designers and developers. I collected their feedback, fixed what annoyed them and announced small updates. Version control in Figma helped us change things safely without breaking live screens.

What I would tell any team

Do not build a design system to look professional. Build it to remove repeated work. Start small, make it easy to find things, and improve it every week. A small system that everyone uses is worth more than a perfect one that nobody opens.