Design Systems · Lesson 01 / 13
Introduction
What a design system is (and isn't), what's inside one, well-known examples, the benefits and costs, when a team needs one, and how to start small.
4 min read · 5 quiz questions
What is a design system?
A design system is a shared set of decisions, reusable components, guidelines and tools that a team uses to design and build products consistently. It is the single source of truth for how a product looks, behaves and is built.
A good definition: a design system is a product that serves other products. It has its own users (designers, developers, content writers, product managers), its own roadmap and its own maintenance — just like any product.
A design system is not finished when it's published. Like any product, it evolves as the products it serves evolve.
Design system vs UI kit vs style guide vs pattern library
| Term | What it is | What's missing |
|---|---|---|
| Style guide | Visual rules: logo, colours, fonts, tone of voice | Components, code and interaction guidance |
| UI kit | A collection of drawn components in a design tool | The rules for using them, code, governance |
| Pattern library / component library | Reusable coded components, often with live examples | Foundations, principles and process may be missing |
| Design system | All of the above, connected: principles, foundations, tokens, components, patterns, documentation, code and governance | — |
What's inside a design system
Principles
A few statements that guide decisions, e.g. "Clarity over cleverness".
Foundations
The basic visual language: colour, typography, spacing, grid, elevation, radius, motion, iconography.
Design tokens
Named values that store the foundations, used by design tools and code: color.action.primary, space.4.
Components
Reusable UI pieces with defined variants, states and behaviour: buttons, inputs, cards, modals, navigation.
Patterns
Recipes that combine components to solve common problems: forms, search and filtering, empty states, onboarding.
Content guidelines
Voice and tone, writing for buttons, errors and empty states, capitalisation, terminology.
Documentation, tools and governance
The website that explains everything, the Figma library and code packages, and the process for contributing and releasing changes.
Well-known design systems
Studying public design systems is one of the best ways to learn. Some widely referenced examples:
| System | Company | Known for |
|---|---|---|
| Material Design | Comprehensive guidance, motion and theming, used across Android and the web | |
| Human Interface Guidelines | Apple | Platform conventions for iOS, macOS, watchOS and visionOS |
| Fluent | Microsoft | Cross-platform design for Windows and Microsoft 365 |
| Carbon | IBM | Enterprise products, data visualisation, accessibility |
| Polaris | Shopify | Merchant admin experiences and excellent content guidelines |
| Primer | GitHub | Developer tools; open-source components |
| Atlassian Design System | Atlassian | Collaboration tools like Jira and Confluence |
| GOV.UK Design System | UK Government | Accessible, research-backed patterns for public services |
Benefits
- Consistency — the same problems are solved the same way across screens, products and platforms.
- Speed — designers assemble screens from existing components; developers reuse tested code.
- Quality — accessibility, responsiveness and edge cases are solved once, inside the components.
- Shared language — designers, developers and product managers use the same names for the same things.
- Scalability — new team members and new products can start fast.
- Easier change — a brand refresh can be rolled out by updating tokens instead of every screen.
Costs and risks
Design systems are worth it for many teams, but they aren't free:
- They take real time to build, document and maintain — often a dedicated team in larger companies.
- A system that doesn't meet product needs gets ignored, and teams build around it.
- Too much rigidity can block innovation; too much flexibility makes it pointless.
- Design and code can drift apart if they aren't kept in sync.
Common mistake: Building a huge design system before having a product. Systems should be extracted from real, repeated needs — not invented in advance for imaginary screens.
When do you need one, and how to start
Signs you need a design system: multiple designers or teams, the same component drawn differently in different places, inconsistent UI in production, developers rebuilding the same things, or a product that will grow across platforms.
- 1Audit your current UI: screenshot every button, input, colour and text style. The inconsistency is usually shocking — and convincing.
- 2Define foundations as tokens: a colour palette, type scale, spacing scale and radius.
- 3Pick the most-used components (often button, input, select, checkbox, card, modal) and design them properly, with all states.
- 4Build them in code with the same names and options as in design.
- 5Document each one briefly: when to use it, variants, do's and don'ts.
- 6Get teams using it, gather feedback, and grow based on real needs.
A useful design system can start with tokens and five well-built, well-documented components. Start small, prove value, then expand.
Key takeaways
- A design system is a product that serves other products: principles, foundations, tokens, components, patterns, docs, code and governance.
- It's more than a UI kit or style guide — the rules, code and process are what make it a system.
- Benefits: consistency, speed, quality, shared language and easier change.
- Costs: time, maintenance and the risk of being ignored if it doesn't meet real needs.
- Start with an audit, tokens and a few core components, then grow from real usage.
Exercise
Run an interface inventory
- Pick a product with many screens (yours or a public one).
- Screenshot every different button style you can find and put them on one board.
- Do the same for text styles, colours and input fields.
- Count how many variations exist for each.
- Propose the smallest set that could replace them all.
Test yourself
Introduction quiz
5 questions. Score 70% or more to complete the lesson.
