A design system is a library of reusable components with rules for how they combine. Done well, the tenth screen costs a fraction of the first. Done on a project that does not need one, it is elaborate preparation for work that never arrives.
The deciding question
How many more screens will exist in two years than exist today? If the answer is 'roughly the same', you do not need a system — you need a well-organised file. If the answer is 'many more, built by people who are not in this conversation', you need a system.
Where it pays for itself
- Products that will keep adding features after launch.
- Anything with more than one team or contractor touching the interface.
- Platforms with client, admin and public-facing surfaces that must feel related.
- Organisations where the developers building screens are not the designers who drew them.
Where it is overkill
- A five-page marketing site that will not change structurally.
- A one-off campaign or landing page.
- An early prototype where the product itself is still being questioned.
A design system is an investment in the screens you have not designed yet. If there are none, there is nothing to invest in.
The middle path is usually right: define your typography scale, colour tokens, spacing and the handful of components that repeat — buttons, inputs, cards — and stop there. That captures most of the consistency benefit for a fraction of the effort, and it can grow into a full system later if the product earns it.
Written by Sky Arkanum · 9 April 2025
Ask us about this