# Design system: what it is and how it works · Zorraquino
> A design system brings together principles, components, styles and documentation to create consistent products collaboratively.
URL: https://www.zorraquino.com/en/dictionary/digital-marketing/design-system.html

# Design system

A design system brings together principles, components, styles and documentation to create consistent products collaboratively

What it means, how it is used and where it comes up, with its related concepts.

[The whole glossary](https://www.zorraquino.com/en/dictionary)

## What it is and how it works

It includes usage guidelines and maintenance mechanisms, as well as visual resources and code. It helps improve consistency and collaboration between design and development. Its usefulness depends on actual adoption and on its ability to evolve with the products.

Topics

[Experience and service design](https://www.zorraquino.com/en/dictionary/category/experiencia-y-diseno-de-servicios)

## Frequently asked questions about Design system

### When is it worth building your own design system?

When there are shared, recurring needs that justify maintaining components, rules and documentation across products or teams. First assess what can be reused and who will sustain the system. For a small product or a one-off piece, an existing foundation or a few conventions may be enough. The decision depends on the intended use and the maintenance effort, not on the size of the library.

### How do you stop every team from creating its own variant of the same component?

You need a contribution process that makes it possible to check whether the need is already covered, propose changes and decide when a variant is necessary. The documentation should explain uses and limits, not just show the component. If the process gets in the way of real work, teams will look for shortcuts; gather that friction and adjust the system rather than demanding uniformity without context.

### How do you know if a design system is actually being used?

Review its presence in real products and the difficulties faced by those who apply it. The number of published components does not prove adoption. Useful signals include effective reuse, recurring exceptions and alignment between design, code and documentation. A system may need fewer components and better guidance; the evaluation should help identify what makes work easier and what forces people to duplicate it.

## Related concepts

- [Responsive design](https://www.zorraquino.com/en/dictionary/digital-marketing/responsive-design.html)
- [Web design](https://www.zorraquino.com/en/dictionary/digital-marketing/web-design.html)
- [Layout grid](https://www.zorraquino.com/en/dictionary/branding/design-grid.html)

## References

- [Design Systems 101](https://www.nngroup.com/articles/design-systems-101/)