Stop calling everything a design system
In short: A Figma component library is not a design system. A real design system needs adoption (the library components are the production components), governance (a named owner who can say no), and a deprecation path. The test - if it disappeared tomorrow and nobody's work slowed down, it's a folder.
Every audit starts the same way. "We have a design system." Great - show me.
What I get shown is a Figma file. Forty components, six of them used, none of them versioned, half detached the moment they hit a real screen. Colours that exist as tokens in the file and as hex codes in the codebase. Two buttons named Button.
That's not a design system. That's a folder.
The deletion test
Here's the test I run, and I'd encourage you to run it honestly: if your design system disappeared tomorrow, would anyone's work actually slow down?
If the answer is no - and it usually is - then it isn't a system. A system is something other things depend on. Nobody depends on a sticker sheet.
What earns the name
Three things, and you need all of them:
- Adoption. The components in the library are the components in production. Not "inspired by." The same ones. If designers and engineers pull from different sources of truth, you have two folders.
- Governance. Someone can say no. New component requests get challenged, duplicates get merged, and there's a named human who owns that unglamorous work. A design system without an owner is a shared drive.
- A deprecation path. Systems that only grow, rot. If you've never deleted a component, you're not maintaining a system - you're hoarding.
Notice what's not on the list: tooling. You can run a real system out of a modest library and a change-log, and you can fail to run one with every plugin money can buy.
Why this matters
The words matter because the budget follows the words. Teams that call a folder a "design system" believe they've done the work, so the actual work - adoption, governance, deletion - never gets resourced. The label becomes the reason the thing it describes doesn't exist.
Build the folder. Folders are useful. Just don't promote it until it passes the deletion test.
FAQ
What is the deletion test for design systems?
Ask honestly: if your design system disappeared tomorrow, would anyone's work actually slow down? If the answer is no, it isn't a system - a system is something other things depend on.
What's the difference between a component library and a design system?
A component library is a collection of parts. A design system is that library plus adoption (production uses the same components), governance (someone owns it and can say no), and a deprecation path. Without all three, you have a folder.
Do I need expensive tooling to run a design system?
No. You can run a real system out of a modest library and a change-log, and you can fail to run one with every plugin money can buy. Tooling is the least important ingredient.