The first time I encountered a proper design system, I thought it was overengineering. Couldn't designers just... design? Did everything need to be systematized and documented? Then I joined a team of twelve designers working on the same product, and watched us ship three different button styles, four heading styles, and seven shades of the same blue. Design systems aren't bureaucracy—they're what prevent creative chaos from consuming your product.
A design system is a shared language. It doesn't limit creativity—it eliminates the need to solve solved problems so you can focus on unsolved ones. When every button doesn't require a decision, you have more attention for the genuinely novel design challenges that actually matter.
Start small. A design system is a living document, not a comprehensive specification. Begin with the components you actually use most: colors, typography scale, spacing, and a handful of core components. Document decisions as you make them rather than trying to document everything upfront. Let the system grow from actual usage rather than predicted usage. The best design systems are the ones teams actually use, not the ones that are theoretically complete.