Design systems explained: what they are and when your product needs one
A design system is a shared set of building blocks and rules for how a product looks and behaves. It lets designers and engineers reuse the same parts instead of rebuilding them, which keeps the product consistent as it grows.
What goes in a design system#
- Foundations. Colours, typography, spacing, icons, and rules for light and dark modes.
- Components. Buttons, forms, menus, tables, cards and other parts, each with its states, such as hover, focus, error and disabled.
- Patterns. How components combine for common tasks, such as signing in, searching or onboarding.
- Guidance. When to use each part, how it behaves, and how to make it accessible.
- Code and design files in sync. The same parts exist in the design tool and in the codebase, so they match.
Signs you need one#
- Screens that should match look slightly different from each other.
- Designers redraw the same button or form for each project.
- Engineers build similar components more than once.
- Changing a colour or a font means searching through many files.
- New team members take a long time to learn how things are done.
When it can wait#
A very small product with one designer and one engineer may not need a full system. A short style sheet with colours, type and a few reusable components is often enough to begin.
How to start small#
- Audit what exists. Collect screenshots of every screen and note the repeated parts.
- Fix the foundations first. Settle colours, type and spacing before components.
- Build the most used components. Start with buttons, inputs and navigation.
- Document the rules in plain words. A short note on when to use each part helps more than a long manual.
- Use it in real work straight away. A system nobody uses goes out of date.
Keep it alive#
A design system needs an owner and a way to make changes. Decide who approves additions, how changes are announced, and how old parts are retired. Review it regularly against the real product.
Accessibility from the start#
Build in clear contrast, visible focus states, keyboard use and readable sizes. It is far easier to include these in the shared parts than to repair every screen later.
Link it to the brand#
A product's design system should come from its brand identity, so the product feels like the same company as the website and the packaging.
If you would like help#
We design and govern design systems and product interfaces. Tell us about your product on the Build With Us page, or see our services.