What is a design system?
A design system is a shared library of reusable components, visual styles and usage rules that designers and developers use to build a product consistently. It typically includes colours, typography, spacing, buttons, forms and patterns, documented once in design files and code so every new screen matches the last.
Updated
| Layer | Examples | Why it matters |
|---|---|---|
| Design tokens | Colours, font sizes, spacing, radius | Change the brand once, update everywhere |
| Components | Buttons, inputs, cards, tables, modals | Build new screens faster with fewer bugs |
| Patterns | Forms, empty states, error messages, M-Pesa checkout | Users learn the product once |
| Guidelines | Tone of voice, accessibility rules, do/don't examples | New team members stay consistent |
When does a business need a design system?
You do not need a full design system for a five-page website. You start to need one when:
- More than one designer or developer works on the product.
- The product has many screens or user roles (admin, staff, customer).
- You run several products that should look related, such as a web dashboard and a mobile app.
- Every new feature seems to introduce a slightly different button or form.
For small products, a lightweight style guide with tokens and a dozen core components is enough. It can grow later.
How is a design system built?
- Inventory. Screenshot every screen and group the repeated elements. Most products have far more button styles than they need.
- Define tokens. Settle the colour palette, type scale and spacing scale.
- Design core components in Figma with their states (default, hover, disabled, error, loading).
- Build the same components in code, for example as React components, so design and code match.
- Document usage with short do/don't examples.
- Govern it. Decide who can add or change components, and review changes.
Common mistakes
- Building a huge system before the product exists. Start small and extract components from real screens.
- Design files and code drifting apart. If the Figma button and the coded button differ, the system has failed.
- No owner. Without someone responsible, the system decays within months.
- Ignoring accessibility at the token level. Colour contrast decided once in tokens is fixed everywhere.
How Mjengo Corporate approaches design systems
For every product we design, we set up tokens and a core component library in Figma as part of the UI/UX blueprint, then mirror it in React code during the build. For larger products and multi-product teams, we scope a fuller design system as a separate piece of work.
Frequently asked questions
Is a design system the same as a style guide?
A style guide documents visual rules such as colours, fonts and logo use. A design system includes those rules plus reusable components in design files and code, and guidance on how to use them together.
Do small startups need a design system?
Not a full one. A lightweight set of design tokens and core components is usually enough for an MVP, and it makes it easier to grow into a full system later.
What are well-known public design systems?
Google's Material Design, Apple's Human Interface Guidelines and IBM's Carbon Design System are widely used public references.
