What a Design System Owes the People Using It
Adoption is the only metric that matters. Everything else is documentation of a system nobody uses.
5 min
read
Design systems are usually evaluated by their coverage. How many components. How many tokens. How complete the documentation. The teams using them evaluate something else entirely: whether the system is faster than working around it. When the system is slower, people route around it. They copy a component and modify it locally. They hardcode a colour. They ship the thing that works. Every workaround is feedback. It marks a place where the system asked for more effort than it returned.
MAKE THE RIGHT THING THE EASY THING
Adoption is not a communication problem. Teams do not skip the system because they forgot it exists.
They skip it because the component does not do what they need, because finding it takes longer than rebuilding it, or because using it requires a conversation with someone who owns it.
Each of those is a design failure in the system itself. The response is not a reminder in a channel. It is removing the friction.
A component that covers eighty percent of cases and composes cleanly for the rest will beat one that tries to cover everything through configuration. Twenty props is not flexibility. It is an unmaintained fork waiting to happen.
SYSTEMS NEED AN EXIT
Every system will encounter a case it did not anticipate. The question is what happens next.
Rigid systems force a choice between waiting for a change and breaking the rules quietly. Both outcomes are bad, and the second is worse because it is invisible.
A good system provides a sanctioned escape hatch: a documented way to build something custom that still inherits the tokens, the spacing, and the accessibility behaviour.
That escape hatch is also a measurement instrument. When several teams reach for it in the same place, the system is missing something real, and now there is evidence rather than opinion.
The goal is not compliance. It is that people choose the system because it is the shortest path to good work.
