A design system nobody uses is a style guide with a nicer website. Adoption comes from making the system the easiest way to build, not from rules.
Start from the code, not the canvas
Components that only exist in a design tool get redrawn in code, slightly differently, every time. Build the coded component first and design from it.
Share tokens, not screenshots
Color, spacing and type as named tokens keep design files and code in step. A rebrand becomes an edit to a few values instead of a hunt across screens.
Make contributing easy
When the system lacks something, teams build their own. A short path to propose, review and publish a new component keeps it growing in one place.
Measure what is used
Count component usage across products. The numbers show where the system helps and which parts need work, better than any survey.