Design System

Design Systems & Engineering • Product Strategy & Growth

A design system is a maintained set of shared decisions, reusable components, and guidelines for designing and building a product or family of products. It gives teams a common way to create interfaces and a process for improving the pieces they share.

What does a design system include?

Part What it helps teams decide
Foundations and tokens Which colors, spacing, and other design decisions to reuse
Components How common controls such as buttons and text inputs look and behave
Patterns and guidance How to combine components for tasks such as entering an address or recovering from an error
Maintenance Who reviews changes, how teams contribute, and how products adopt updates

Start with the parts your teams repeatedly need. The GOV.UK Design System is a public example with styles, components, patterns, and contribution criteria.

Design system vs. component library vs. UI kit

A UI kit typically provides reusable design assets in a design tool. A component library provides reusable interface components. A design system connects those assets and implementations to usage guidance and maintenance. A team can use a library from another organization and document the additional decisions its own products need.

Example of a shared button

Suppose two teams use a primary button in checkout and account settings. They agree on how the button presents a label and keyboard focus, which tokens it uses, and when a secondary action should have less visual emphasis. The component library provides the implementation. The system documents when to use it and how to request a change.

If checkout introduces a pending state, the teams review what happens to the label, feedback, and repeat submissions. They decide which behavior belongs in the shared component and which belongs to checkout. They test the button in both products. Checkout owns the payment request and its outcome, while the system can document how the button presents a pending action.

How do you start a design system?

Pick one recurring pattern with a clear owner and two real places to try it. Document what should stay consistent and what product teams can configure. Check the result in context and record how consuming teams will get future fixes. Use feedback from the first two implementations to decide what to document or share next.

Sources