A component library
A component library typically makes decisions for one group or discipline, with a narrow purpose — for example, improving code efficiency, developer experience, or maintaining a Figma UI kit.
A code-side example: increasing shared dependencies to reduce maintenance burden, such as a standalone button component reused across pagination, address search, and tab patterns.
A design system
“Design systems are culture change disguised as a UI kit.”
— @laurenloprete, Figma Schema 2022
A design system is an operating framework and set of standards for an organisation to deliver repeatable decisions across the entire product lifecycle — for all digital disciplines (Product, Design, Engineering).
Each decision is a principled marker specific to the company’s ways of working and products at that point in time.
A design system typically aims to improve:
- Product UI cohesion — consistent experiences across surfaces
- Colleague experience and education — a shared language and way of working
- Delivery efficiency — predictable cadences, reduced duplication
Systems constraints enable more consistent outcomes. They free teams to channel more effort into solving user problems rather than re-solving solved ones.