Does my business need a design system?
Short answerAlmost every business needs the basic level: written rules for its logo, colours, typefaces, photography and tone of voice, plus a website built from reusable sections that follow them. Few small businesses need the full component libraries software companies maintain. You need more system as more people, suppliers and pages produce material in your name.
Key points
- A design system is a set of reusable decisions, written down, so anyone can produce material that looks and sounds like you.
- Without one, identities drift through small exceptions, and the drift is usually visible within months of launch.
- Most small businesses need a one-page brand sheet and a website built from a few reusable sections, not a software-style library.
- The test of any system is simple: can someone else build a new page that still looks like you?
The term comes from software companies, where hundreds of designers and engineers build screens that have to match, and it can sound like something only they need. The problem it solves is universal, though: once more than one person produces material in your name, the brand starts to drift. This guide explains what a design system is, why the drift happens, and how much system a business of your size genuinely needs.
What is a design system, in plain English?
A design system is the set of decisions that make your business look and sound like itself, written down and turned into parts people can reuse. It has four layers:
- Foundations. The logo and its versions, the exact colour values, the typefaces and how each is used, spacing, and the style of photography. On a website these are often stored as design tokens, which are named values such as "brand green" set once and used everywhere, so changing one value updates every page.
- Components. The reusable parts built from those foundations: buttons, page headers, a review block, a case study layout, a proposal template, a social post template.
- Rules for use. When to use which part, and what not to do: the logo never on a busy photograph, the accent colour only for the main action, no more than one headline size per section.
- Voice. How you write: the words you use, the ones you avoid, and an example paragraph in the right tone.
Brand guidelines usually cover the first and last layers. A design system adds the working parts in the middle, which is what makes the rules easy to follow rather than easy to ignore.
Why do brands drift without one?
Every identity gets tested about six months after launch. Two businesses can launch new brands on the same day with the same ambition. What separates them later is whether anything was holding the identity together underneath.
Without a system, the pattern is predictable. In the first month, the first exception is approved, just this once: a slightly different button for a special offer. By six months, a second blue has appeared and nobody remembers choosing it. A supplier made a brochure from an old logo file. A new member of staff built a landing page in whatever looked nice. By the second year, the real brand lives in a folder no one can find, and the business is paying to rebuild it from scratch.
With a system, the same six months look different. A new page ships already knowing how to behave. Someone other than the original designer builds a page, and it still looks and sounds like you. Two years on, the system has outlived the brief that created it.
The test of a design system is not how it looks at launch. It is whether someone else can build a new page six months later and it still looks like you.
How much system does your business need?
Think of it in three levels. Most businesses need the first, many growing ones need the second, and few need the third.
| Level | What it includes | Who needs it |
|---|---|---|
| 1. Brand sheet | Logo files and rules, a small palette with exact values, two typefaces and their uses, photography style, a short voice guide | Every business, including sole traders |
| 2. Working system | Level 1, plus a website built from reusable sections, document and social templates, and a short list of approved components | Businesses where several people or suppliers produce material, or that add pages and campaigns regularly |
| 3. Full design system | A documented component library in a design tool and in code, with versions, an owner and a process for changes | Software products, multi-brand groups, organisations with in-house design and engineering teams |
The common mistake runs in both directions. Small businesses buy a sixty-page brand book that nobody opens, which is level 3 effort with level 1 benefit. Growing businesses stay on a single logo file long after five people are making material, and pay for it in drift.
What are the signs you need more than you have?
- Your proposals, invoices and presentations each look slightly different.
- Suppliers keep asking for "the logo", and you are not sure which file to send.
- Every new web page takes as long as the first, because each one is designed from scratch.
- Social posts are made in different apps by different people and do not look like one business.
- Your ads send people to pages that do not match the main website, which makes buyers wonder whether they have landed in the right place; the guide to landing pages for Facebook ads explains why that costs enquiries.
- Someone has to "check with the designer" before anything simple can go out.
How do you build level one yourself?
A brand sheet is an afternoon's work for most owners, and it prevents most of the drift described above.
- Gather everything. Collect every item that carries your logo: website screenshots, proposals, signage photos, social profiles, vehicle livery.
- Choose the best version of each element and retire the rest. One logo in three formats: horizontal, stacked, and a small mark for profile pictures.
- Write down exact colour values. Hex codes for screens, and print values if you print. Four or five colours, most of them neutral, is plenty.
- Pick two typefaces and say what each is for: one for headlines, one for everything else.
- Describe your photography in three rules, such as real work only, natural light, no people posed with thumbs up.
- Write the voice guide. Five words you use, five you avoid, and one paragraph rewritten in the right tone.
- Name an owner and put it in one shared place that everyone, including suppliers, can reach.
Sample business. Hartwell Joinery, a bespoke kitchen maker in Leeds since 2009, fits its brand sheet on one page. The palette is four colours: Forest for the logo and headlines, Brass for the single main button on any page, Clay for backgrounds behind reviews, Paper for everything else. One serif for headlines, one plain typeface for everything else. Photography is finished Hartwell kitchens in daylight, never stock. The voice guide says "workshop", "made" and "fitted", and avoids "solutions" and "passion".
When a new fitter joins and makes an Instagram post, or a printer asks for files, the answer is the same page. Nobody needs to ask the designer.
What does a design system look like on a website?
On a website, a working system means pages are assembled from a set of tested sections rather than designed one at a time. A homepage hero, a service section, a review strip, a case study block, a contact panel: each built once, to the brand's rules, and reused. Whoever edits the site chooses from those sections and cannot pick a random colour or font, which is the point.
This has practical benefits beyond looks. New pages are faster and cheaper to add. The site stays consistent when someone other than the original builder edits it. And consistent structure, with headings and layouts that behave the same way on every page, makes the site easier for search engines to read. Design systems and performance were a large part of Muhammad Afzal's work as a senior frontend engineer before founding M/AFZAL, and the same thinking scales down to a five-page business site.
The best moment to introduce one is during a redesign, because retrofitting a system onto a site where every page was built differently is often more work than rebuilding. If you are planning one, the guide to redesigning a website without losing SEO covers how to protect your rankings while you do it, and moving off Wix, Squarespace or WordPress covers the platform question.
When is a design system overkill?
- When the positioning is not settled. A system locks in decisions. Lock in the wrong ones and you have made them harder to change. Settle your positioning first.
- When the identity itself is about to change. If you are deciding between a rebrand and a refresh, build the system as part of that work, not before it.
- When it is bigger than the business. A component library with versioning for a five-page site and one person posting on Instagram is cost without benefit.
- When the rules allow no exceptions at all. A good system has a way to add something new. A rigid one gets ignored the first time it is inconvenient.
For most established businesses, the right answer is level one this month, and level two the next time the website is rebuilt. Both sit inside the larger job of making the business look like the premium choice every time a buyer meets it.
Straight answers.
The follow-up questions owners ask most.
- Is a design system the same as brand guidelines?
- Brand guidelines are part of one. Guidelines describe the rules; a design system also includes the working parts, such as website sections, document templates and colour values set in code, that make following the rules the easy option.
- Do I need Figma to have a design system?
- No. Figma is a common tool for designing and sharing systems, but a small business can run well on a shared document, a set of templates and a website built from consistent sections.
- Can I add a design system to my existing website?
- Yes, if the site was built from reusable sections or a theme you control. If every page was built by hand in a different way, it is usually cheaper to define the system now and apply it during the next redesign.
- Who should own the design system in a small business?
- One named person. Someone has to approve exceptions and keep the rules up to date, and when everyone owns the system, nobody does.