UX Glossary · D
Design system
The components, tokens, patterns and rules a product is assembled from, kept in sync between design and code.
A design system is the shared vocabulary a product is built from: design tokens, components, patterns and the rules for using them. Crucially it exists in both design and code, and the two stay in sync.
It is more than a style guide, which documents appearance. A design system includes working components and the decisions about when to use them.
What makes one succeed
The systems that work have a few things in common: they are used by the teams they were built for, they are versioned, and someone owns them. The ones that fail are usually a beautiful Figma library nobody in engineering references, so the code drifts and the library becomes a description of a product that no longer exists.
That drift is the single most common failure, and it is organisational rather than technical. A system without a maintainer decays into documentation.
Rules matter more than components
A button component is easy. The rule that there is exactly one primary action per view is what actually produces consistency, and it is the part most systems under-document. Rules survive contact with new screens; components only cover screens you anticipated.
In practice
Start from an inventory of what already exists rather than from a blank canvas. Most products already have a system, undocumented and contradictory, and writing down what is actually in use is a faster route to consolidation than designing an ideal one.