Design systems for small teams
What a design system is, how a small team can start with a handful of reusable parts, the consistency it brings and when it is overkill.
A design system is a set of reusable parts, plus the rules for using them. Buttons, colours, type sizes, form fields, spacing. Decide each one once, write it down, and use it everywhere. That is the whole idea, and it is less grand than the name suggests.
Big companies have entire teams devoted to theirs. A small business does not need that. It may still benefit from a very small version.
What problem does it solve?
Look closely at almost any website or app that has grown over a few years and you will find drift. Four slightly different blues. Buttons with square corners on one page and rounded on another. Headings in three sizes that were each somebody's best guess on the day.
No single inconsistency matters much. Together they make a product feel patched, and they cost real time. Every new page starts with the same small decisions: how big is the heading, what colour is the link, how much space goes under the image? Made fresh each time, by different people, those decisions never quite match.
A design system makes them once. After that, building a new screen is closer to assembling than inventing.
What is in one?
Think of it in three layers.
The basics
Designers sometimes call these foundations or tokens. They are the raw ingredients.
- Colours. Your brand colours, a set of greys, and colours for success, warning and error.
- Type. One or two typefaces and a fixed scale of sizes for headings, body text and small print.
- Spacing. A short list of allowed gaps, so everything lines up on the same rhythm.
- Corners, borders and shadows. One agreed treatment for each.
Components
The reusable building blocks made from those basics.
- Buttons: primary, secondary and a quiet text version
- Form fields, checkboxes and dropdowns, including their error states
- Cards, such as a product, a team member or a booking
- Navigation: header, menu, footer
- Alerts and messages
Guidance
Short notes on when to use what. "One primary button per screen." "Error messages sit under the field." "Photos are always wide format with rounded corners." A sentence or two each is enough.
How does a small team start?
Start tiny. The mistake is trying to document everything before you have built anything.
- Take stock of what exists. Screenshot every button, heading and form on your current site or app and put them side by side. The inconsistencies will be obvious, and slightly embarrassing.
- Pick the survivors. Choose one version of each and retire the rest.
- Write down the basics. Colours with their exact values, type sizes, spacing steps. One page.
- Define five to ten components. The ones you use constantly: button, text field, card, heading styles, link.
- Put it somewhere everyone can find. A shared page or a file in your design tool. If people cannot find it in ten seconds, they will guess instead.
- Use it on the next piece of work. A system proves itself when it makes a real page faster to build.
Then let it grow only when needed. When you find yourself designing something for the third time, that is the signal to turn it into a component. Not the first time, and usually not the second.
What do you get back?
- Speed. New pages and screens come together faster because the pieces already exist.
- Consistency. Customers learn how your product works once, and that knowledge carries across every screen.
- Easier changes. Update the primary colour in one place and it changes everywhere, provided the system is built into the code as well as the designs.
- Smoother handovers. A new designer, developer or agency can pick up where the last one left off. For a small business that changes suppliers now and then, this alone can justify it.
When is it overkill?
Often, to be honest. A design system is an investment that pays off through reuse. No reuse, no payoff.
You probably do not need one if:
- You have a five page website that changes twice a year.
- One person does all the design and build, and holds the rules in their head.
- Your site runs on a template that already enforces consistent styles.
In those cases, a one page style sheet listing your colours, fonts and button style is plenty.
You probably do need one if:
- You have a website and an app, or several products, that should feel related.
- More than one person designs or builds for you.
- You add new pages or features regularly.
Questions to ask your designer or agency
If someone else is building your site or app, you can still make sure you benefit.
- Will the design be built from reusable components, or page by page?
- Will I receive a style guide or component library at handover?
- Are the colours, type sizes and spacing defined in one place in the code?
- If I want to add a page next year, can it be assembled from what already exists?
You do not have to manage the system yourself. You only need to know it exists, that you own it, and that the next person who works on your product will be handed it on day one.