IT Glossary
What is a design system?
The collection of reusable rules and visual components a team builds interfaces from: buttons, colours, typography, spacing and the guidance for using them.
Count how many slightly different blue buttons live across your website, your customer portal and your mobile app. In most companies the honest answer sits somewhere above a dozen, each drawn from scratch by whoever was on the project that quarter, each behaving a little differently on a phone. A design system is the antidote: one documented set of building blocks — colour tokens, typographic scale, spacing rules, form fields, buttons, tables, dialogs — implemented once in real code and reused everywhere, together with written guidance on when each is appropriate. It is not a style guide sitting in a slide deck; the components are the deliverable and the documentation exists to explain them. The commercial argument is compounding rather than immediate. The first project pays for the system and gains little. From the second onward, new screens get assembled rather than drawn, accessibility and keyboard behaviour are inherited instead of re-argued, and a brand refresh becomes a change to shared values rather than a hunt through every page. For a company that expects to keep building, that is the difference between owning an asset and repeatedly renting one.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
New screens in days, not weeks
Assembling from tested components removes the design, build and review cycle that every fresh interface element otherwise triggers.
One brand at any scale
Website, portal and app stay visually identical even when different teams or suppliers work on them in different years.
Accessibility solved once
Contrast, focus order and keyboard support are built into the components, so every new screen inherits compliance by default.
Frequently asked questions
How does a design system differ from a brand manual?
A brand manual describes intent in a document: logo clearances, palette, tone of voice. A design system delivers working code — a button a developer imports, with its states, sizes and accessibility behaviour already decided. The manual tells you what good looks like; the system makes producing anything else the harder option.
Is a design system worth it for a single website?
For one small brochure site, no — the overhead outweighs the return. It starts paying when you have a second surface: a customer portal, a mobile app, a partner extranet, or simply a site that will keep growing for years with rotating suppliers. Break-even usually arrives around the third significant project on the same brand.
Which well-known design systems can we learn from?
Publicly documented examples are worth reading before commissioning your own: Google's Material Design, IBM's Carbon, Atlassian's system, Shopify's Polaris and the UK Government Design System. The last is particularly instructive because it publishes the user research behind each decision, which is the part most internal systems skip.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247