The term design system gets used for very different things. To one person it is a Figma library full of buttons, to another a PDF with logo rules. Both have a point, but they are not describing the same thing. If you want a design system built, it pays to know first which problem it should solve.
In short: a design system is a coherent set of design decisions, files and rules that lets several people apply the same brand consistently. What sets it apart from a stand-alone visual identity is that last part. A system is made to work with, not just to look at.
Four things that often get mixed up
We distinguish four concepts. An organisation rarely needs all four to the same degree, but it helps to keep them apart.
1. Brand identity
The identity defines character and recognition: logo, typography, colour, imagery, shapes and the way they come together in a composition. This is the creative core. Without a strong identity, a system is mostly a tidy collection of something forgettable.
2. Brand book or guidelines
The brand book explains how the identity is applied: clear space around the logo, colour use, examples of right and wrong. A good brand book is useful, but it often remains a document people work around. It describes rules; it does not provide building blocks.
3. Digital design system
A digital design system holds reusable values and parts: design tokens, components such as buttons and forms, patterns for complete pages and documentation on behaviour and accessibility. Product teams use it in Figma and in code. Well-known public examples are IBM Carbon, the GOV.UK Design System and NL Design System.
4. A system agents can use
More and more material is created with the help of AI tools. Those tools need the same information people do, only explicit and machine-readable: tokens, components, recipes for recurring tasks and examples with explanations. This does not replace the other three layers. It makes them reachable for a specific workflow.
What goes into a usable design system?
The exact contents differ per organisation. A consultancy that mainly produces proposals and decks needs something different from a software company with hundreds of screens. Still, these parts almost always come back:
- Design principles that lead to decisions, not just adjectives.
- Canonical logo files with variants, clear space and minimum sizes.
- Typography and colour as named roles, with checked contrast.
- Composition rules: grid, white space, image ratios and what happens with long text.
- Templates for the material your team actually makes.
- An organised library with clear file names and ownership.
- A version number and a changelog, so everyone knows what is current.
When do you need one?
Not every organisation needs an extensive system. These signals tell you it is time:
- Several people or agencies produce material, and it always looks slightly different.
- Your designer is the bottleneck: without them, nothing good leaves the building.
- Files are impossible to find or exist in five versions.
- Your website, decks and product do not look like they belong to the same company.
- Your team uses AI tools, but the results do not fit your brand.
And when not yet
Just getting started and producing only a few kinds of material? Then a strong identity with a handful of good templates is often enough. A system grows with what you actually make. Starting with a complete component library nobody uses is money wasted.
The reverse is true as well: a system does not fix a weak identity. If the way you look no longer matches the quality of your work, start with the design. Only then does it pay to document everything carefully.
Where do you start?
- Take stock of what your team makes. Which five pieces come back most often?
- Look honestly at your identity. What is strong, what is missing, what needs to change?
- Capture the key decisions as roles and rules, with examples.
- Build templates for those five pieces and test them with the people who will use them.
- Name an owner and agree how changes are rolled out.
The best test for a design system: can someone who did not build it create a good new piece with it, without having to make the same design decisions all over again?
At undesign we always start with the work itself. First a convincing identity, then the system that makes that quality usable for your team, your agencies and your tools.
