Branding
Design system
A design system is a library of ready interface elements together with rules for using them, so a website and an app look and behave consistently. Unlike a brand manual it is not read but used: it holds components a developer drops straight in.
What it means in practice
It holds buttons, forms, cards, alerts and the states they can be in, plus defined spacing, type sizes and colours as variables. It exists twice: as a library in the design tool for the designer and as components in code for the developer. When those two halves drift apart the system stops working and becomes a gallery. A first version for an ordinary corporate site takes two to three weeks.
Why it only pays above a certain size: on a five page website it is pure overhead. Once a company has a site, a shop, a customer area and a mobile app it starts to pay, because a new page is assembled rather than designed. Changing the primary colour becomes one edit instead of four projects. It also speeds up onboarding a new supplier, who no longer has to guess what a button should look like.
How to get one: do not start from scratch, start with an inventory. Export every button and form you already have. There are usually twenty and two of them genuinely differ. Unifying the rest is the basis of the system. Then add rules for the states everyone forgets: what someone sees on an error, while loading, and when a list is empty.
Where it goes wrong: a system built upfront for everything the company might one day need. You get a library of a hundred components, fifteen of which are used, and nobody maintains it. The second mistake is a system with no owner. With nobody responsible, within six months every project makes its own exception and you are back where you started.
We add a new component only the third time it is needed. Twice is coincidence, three times is a pattern. Try it today: look at your website and count how many different buttons are on it.