What actually moves the needle in a design system

Everyone starts a design system with components. Buttons, inputs, cards — the visible layer. That part is necessary but it's not what determines whether the system is still being used in eighteen months.

What determines that is governance: who can propose a new variant, how a breaking change gets communicated, and whether teams can pin to a version instead of being forced onto main. Without that, a design system degrades into a shared node_modules folder that everyone is quietly afraid to touch.

The other underrated piece is documenting the reasoning, not just the API. A component's props tell you how to use it; they don't tell you when not to. The design system that actually reduces effort is the one where an engineer can answer 'should I use this or build something custom' without pinging the platform team.