What Is a Design System, and Do You Need One?
A design system is tokens, components, patterns, documentation and an owner. Here is how to tell whether your product needs one now, and whether to adopt, extend or build it.

Key takeaways
- Nielsen Norman Group's Design Systems 101 describes a design system as two things: a design repository (style guide, component library, pattern library) and the people who manage it.
- The W3C Design Tokens Community Group published the first stable version of its token format, 2025.10, on October 28, 2025. It is a Final Community Group Report, not a W3C Standard, and it was still the latest stable version on November 18, 2026.
- In zeroheight's Design Systems Report 2026, a survey of 147 practitioners, 83% of organizations had a dedicated design system team, 3 in 5 teams were understaffed and 7% said their system was fully adopted.
- Two small experiments measured speed: in Figma's 2019 test designers finished 34% faster with a design system, and Sparkbox's 2021 study of eight developers reports that a simple form page was 47% faster to develop with IBM's Carbon.
- A design system does not make a product accessible by itself: GOV.UK says using its design system "does not immediately make that service accessible", and the U.S. Web Design System says its components do not guarantee an accessible service.
A design system is the shared set of parts and rules a product is built from: design tokens, components, patterns, documentation, and the people and process that keep them current. Nielsen Norman Group describes it as two things: a design repository and the people who manage it. Your product needs one when several designers and developers build more than one product or platform from the same parts. Before that, a UI kit on an open component library is enough. Budget for the upkeep first: in zeroheight's Design Systems Report 2026, a survey of 147 practitioners, 3 in 5 design system teams were understaffed.
This guide is for founders, product managers and heads of product in the US and the UAE who hear "we need a design system" from designers or developers and have to decide whether to pay for it. Inside: the parts in plain words, the difference from a style guide, a UI kit and a component library, the signals that you need one, public systems to build on, the design tokens format as of November 18, 2026, upkeep, and the evidence on speed, accessibility and AI coding tools.
What is a design system?
It is one source of truth for how your product looks and behaves, used by both design and code. Five parts make it up.
- Design tokens. Named values for color, type, spacing, corner radius and motion.
- Components. Buttons, fields, tables and dialogs, each with every state: hover, focus, disabled, error, loading, empty.
- Patterns. How components combine to solve a task: a sign-up form, a filter bar, an empty screen.
- Documentation. When to use each part, and when not to.
- Rules for change. Who owns the system, how a new component gets in, and how new versions reach the products.
Nielsen Norman Group groups the same things differently: a style guide, a component library and a pattern library form the repository, and a team manages it. The team is the part buyers skip. Without an owner, the files drift away from the product.
The practical test is whether design and code agree. Our product design service defines the deliverable as components, tokens and rules in Figma that match the components in your code. If the button in Figma and the button in the code only share a name, you have a UI kit and a codebase, not a system.
Design system vs style guide vs UI kit vs component library
Vendor quotes use these terms as synonyms. They are not, and the difference decides what you pay for.
What each term covers. The style guide row follows Nielsen Norman Group's Design Systems 101; "UI kit" and "component library" are defined the way we use them. Checked November 18, 2026.
| Term | What it is | What it leaves out | Enough when |
|---|---|---|---|
| Style guide | Guidelines, visual references and design principles: colors, type, logo, tone | Working components and code | You have a brand, a marketing site and decks |
| UI kit | Components and styles drawn in a design tool such as Figma | Code, usage rules, a release process | One product and one small team, around launch |
| Component library | Reusable interface elements as working code | Design files, patterns, rules on when to use what | Developers lead and the interface is simple |
| Design system | All of the above, tokens shared by design and code, an owner and a process for change | Nothing by scope; it costs the most to keep | Several products, platforms or teams build from it |
Vendors blur the terms too. The documentation of shadcn/ui, an open set of React components, says: "This is not a component library. It is how you build your component library." So when a quote says "design system", ask which rows of this table it includes, and whether the parts will exist in code or only in Figma.
What are design tokens?
A design token is a design decision with a name. The Design Tokens Community Group at the W3C defines a token as "information associated with a human readable name, at minimum a name/value pair".
Without tokens, the brand blue is a color code typed into dozens of files. With tokens, one entry named something like color.action.primary holds the value, and buttons, links and charts point to the name. Change the value once and every place follows. A rebrand, a dark theme or a second brand becomes a new set of values, not a redraw of every screen.
Material Design says "the same tokens are used in designs, tools, and code". The U.S. Web Design System calls its tokens "a limited set of discrete options, just like a scale of musical notes". That is the business point: fewer choices, so two designers pick the same spacing value.
Is there a standard format for design tokens?
There is a stable shared format, but not a formal W3C standard. On October 28, 2025 the Design Tokens Community Group announced the first stable version of its specification, 2025.10, and called it "a production-ready, vendor-neutral format for sharing design decisions across tools and platforms". The announcement says more than 10 design tools and open-source projects support it or are implementing it, and names Figma, Penpot, Sketch and Framer among them.
The status matters when someone calls it "the W3C standard". The Format Module is a Final Community Group Report. Its status section says it is "not a W3C Standard nor is it on the W3C Standards Track", and that the specification is considered stable. It is a format the tool makers agreed on, not a standard of the rank of WCAG. As of November 18, 2026, version 2025.10 is still the latest stable one; the group's draft is marked as a preview that should not be implemented.
What to do with this: ask for your tokens as files in this format, kept in your own repository, so the values are not locked inside one design tool. The zeroheight report shows where teams stop: 86% of the surveyed design systems include tokens, but only 40% of teams automate the sync between design tools and code.
Do I need a design system?
Our service page gives the short answer: yes, when the product will grow or several teams build it. The signals that the time has come:
- More than one product or platform. A web app, an iOS app and a marketing site that should look like one company.
- Several designers and developers in parallel. Each makes the same small decisions again, differently.
- The same button built several times. Every fix has to be made in every copy.
- Slow, inconsistent releases. Each new screen starts from a blank page.
- Accessibility debt. Contrast, focus and target-size problems repeat on every page because they sit in the shared parts.
- A change that touches everything. A rebrand, a dark theme, a white-label version, or Arabic with a right-to-left layout for the UAE.
And these say you do not need one yet:
- One landing page or a small marketing site. A style guide covers it.
- A product before its first users. The screens will change after the first feedback.
- One designer and one developer. They agree in a chat.
That is how we worked on NVP, a fintech product: we designed on its own shadcn/ui components, so the first redesign ran in its code the next day. The project ran on a UI kit, not a custom design system. Our fintech dashboard design guide has the details.
Design system examples: adopt one, extend one or build your own?
You rarely start from zero. Large companies and governments publish their systems.
Public design systems in their own words, from their documentation, checked November 18, 2026.
| System | Owner | How it describes itself | What you get |
|---|---|---|---|
| Material Design 3 | "Google's open-source design system" | Guidelines, styles and components for Android, Flutter and the web | |
| Human Interface Guidelines | Apple | "Guidance and best practices" for any Apple platform | How to use and customize the system-defined components |
| Fluent 2 | Microsoft | "Microsoft's design system" | Components for the web (React, Web Components), iOS, Android and Windows |
| Carbon | IBM | "IBM's open-source design system for products and digital experiences" | Working code, design tools, human interface guidelines |
| U.S. Web Design System | U.S. General Services Administration | "The design system for the federal government" | Components for accessible, mobile-friendly government sites; contributors support nearly 200 sites |
| GOV.UK Design System | UK government | "GOV.UK styles, components and patterns" | Reusable, accessible components for forms, navigation and tables |
| shadcn/ui | Open-source project | "How you build your component library" | The actual component code, copied into your project |
That leaves three ways to get a system.
Three ways to get a design system. The order of cost follows Nielsen Norman Group's Design Systems 101; the rest is our assessment. Checked November 18, 2026.
| Adopt an open system as is | Extend an open system | Build your own | |
|---|---|---|---|
| What you do | Use its components and rules unchanged | Keep its components, replace the tokens with your brand's, add what is missing | Design and code every token, component and pattern |
| Time and money | Lowest: "the lowest-cost approach", which "requires the least time to implement" | Middle: the savings shrink as your changes grow | Highest: "the more custom" the system, "the more time and money it will take" |
| What you give up | Your product looks like others on the same system | You follow upstream releases or freeze your copy | Nothing in looks; all upkeep and accessibility testing is yours |
| Fits | Internal tools, admin panels, early products | Most SaaS products and apps with their own brand | Several products, a strong brand, needs an open system cannot meet |
For most products we see, extending is the right answer: keyboard behavior, states and accessibility come ready, and the brand goes on top through tokens.
A brand can be reason enough to build your own, on a small scale. For RYTM, a wellness brand, we built a design system of 101 tokens and 6 component families, with a live styleguide for every component and a guidelines page with logo downloads. The site and blog run on it, and six sales decks reuse the same palette, type and wordmark. It is a brand and website system, not a multi-platform product system. What carries over is the order of work: tokens first, a few component families, a live reference page anyone can open.
How long does it take to build a design system, and what does it cost?
We give no figures here, on purpose. We did not find a published survey with a sound sample for the time or cost of building a design system; the numbers that circulate come from vendor blogs with no stated method. The one sourced statement is the order of cost in the table above. For design work in general, our UI/UX design cost guide lists market rates from Clutch, Upwork and the US Bureau of Labor Statistics. Those are market figures, not our price list.
What drives the size of the work:
- Components and states. Thirty components with six states each is a different job from ten with three.
- Platforms. Web only, or web plus iOS and Android.
- Themes, brands and languages. Dark mode and white label multiply the token sets; Arabic needs mirrored components.
- Code parity. Figma only, or coded and tested components that match it.
- Documentation. A page of rules per component, or a name and a picture.
- Migration. Moving the screens you already have onto the new parts.
A design system is never finished, so ask for the scope of the first release: which components, on which platforms, with what documentation.
What does it take to keep a design system alive?
An owner. One named person or team decides what goes in. In the zeroheight report, 83% of organizations have a dedicated design system team, and still 3 in 5 teams are understaffed. Only 7% of respondents say their system is fully adopted across all teams. Mind the limits: 147 self-selected practitioners, 39% of them from organizations of 5,000 or more people, surveyed by a vendor of design system documentation software.
Versions. A change to a button reaches every screen that uses it, so changes ship as numbered releases, the way the U.S. Web Design System and GOV.UK publish theirs.
A contribution process. Teams will need components the system lacks. GOV.UK publishes its criteria: a proposal must show the component or pattern is useful and unique; before publication the team checks it is usable, consistent and versatile. A small company needs a lighter version: a place to propose and a person who decides.
So ask who will own the system a year after it ships. If nobody can answer, build a UI kit and come back to the question later.
Does a design system speed up development?
The evidence says yes, and it is thinner than the claims around it. We found two experiments with a published method, both small.
- Figma, 2019. In a test with Figma's own designers, participants "completed their objective 34% faster" with a design system. The system fit the task exactly, and Figma expects that to be the maximum saving in real work.
- Sparkbox, 2021. Eight developers coded a simple form page from scratch and then with IBM's Carbon. The authors write that the system made the page "47% faster to develop" and separately give medians: 4.2 hours from scratch against 2 hours with Carbon, learning time included. They call it "a small study of a handful of excellent developers".
Our own data point is one team as well. At Leeloo.ai, a design system built by Artsiom Yankovich, our Head of Design & Strategy, cut landing page production time by 60%. Landing pages repeat the same blocks, which is where a system helps most.
Does a design system make a product accessible?
It makes accessibility cheaper to reach. It does not deliver it. WCAG 2.2, a W3C Recommendation since October 5, 2023, added criteria that belong in components: a pointer target of at least 24 by 24 CSS pixels, and a focused element that is not entirely hidden by other content. Set those once in the button, the link and the field, and every screen inherits them.
GOV.UK states that using its design system "does not immediately make that service accessible". The U.S. Web Design System, which works toward WCAG 2.1 AA and as much of 2.2 as it can, says that building with its components "does not guarantee an accessible service". In the Sparkbox study, two developers' from-scratch pages beat the design system versions on accessibility.
Components fix the repeated errors; people still test the pages. Our ADA website compliance guide covers the legal side and the order of fixes.
Do AI coding tools need a design system?
They work better with one, in the first published test we could find. On August 5, 2026 Figma published an evaluation of 27 design-to-code tasks on two React design systems. When the AI agent could see how the Figma components map to the real code components, the median task took 19.6% less time and 29.5% fewer tokens (units of AI model usage, not design tokens), and code quality rose by one point on a four-point scale. The limits: a vendor's test of its own product, on two systems, scored by AI judges.
An AI tool with no components to reuse writes a new button every time, which is the problem a design system exists to remove. Teams are early here: in the zeroheight report, 10% have built AI into their design system processes and 46% are experimenting.
Our Head of Design & Strategy works with AI agents so that research, prototype and build run as one loop. A loop like that needs parts to reuse, one more reason we start with tokens and components. If your interface was generated without shared parts, our guide to taking a vibe-coded app to production lists what else to check.
Checklist: how to decide and what to ask for
- Count the surfaces. Products, platforms, brands and languages that must look like one company.
- Count the people. Designers and developers who build in parallel.
- Pick the level. Style guide, UI kit, component library or full system, using the first table.
- Pick the route. Start from an open system unless you can name what it cannot do.
- Ask for tokens as files. In the Design Tokens Community Group format, in your repository.
- Ask for parity. Components in the design tool that match components in code, with every state.
- Set the accessibility target. WCAG 2.2 AA, tested per component and again on real pages.
- Name the owner. Who decides, and how changes are released.
- Scope the first release. A list of components, not "a design system".
We build design systems as part of product design, for web, iOS or both. A UX audit shows where the interface is inconsistent today. Or tell us about your product, and a partner will say which level you need now.
Questions we get asked
What is a design system in simple terms?
A design system is the shared set of parts and rules a product is built from: design tokens (named values for color, type and spacing), components with all their states, patterns, documentation, and an owner with a process for changes. Nielsen Norman Group describes it as a design repository plus the people who manage it. The practical test is whether the components in the design tool match the components in the code.
Do I need a design system for a startup or an MVP?
Usually not yet. Before the first users, screens change too often for a full design system to pay off. A UI kit on an open component library such as shadcn/ui, with your own tokens for color, type and spacing, is enough and can grow into a system later. You need a design system when several designers and developers build more than one product or platform from the same parts.
What is the difference between a design system and a UI kit?
A UI kit is a set of components and styles drawn in a design tool such as Figma. A design system includes that and adds what a UI kit lacks: the same components as working code, tokens shared by design and code, documentation on when to use each part, an owner, and a process for releasing changes. A style guide covers only the visual rules, and a component library covers only the code.
What are design tokens, and is there a standard format?
Design tokens are design decisions stored as named values, such as a color or a spacing step, that both design tools and code read. The W3C Design Tokens Community Group published the first stable version of its format, 2025.10, on October 28, 2025, and named Figma, Penpot and Sketch among the tools that support it or are implementing it. It is a Final Community Group Report, not a W3C Standard. On November 18, 2026 it was still the latest stable version.
How long does it take to build a design system, and what does it cost?
There is no reliable published benchmark: we found no survey with a sound sample for the build time or cost of a design system, so we quote none. The size of the work depends on the number of components and states, the platforms, themes and languages, whether components are coded or exist only in Figma, the depth of documentation, and the migration of existing screens. Nielsen Norman Group ranks adopting an existing system as the lowest-cost route and a custom system as the most expensive.
Can we use Material Design or another open design system instead of building our own?
Yes, and for most products it is the sensible start. Material Design 3 and IBM's Carbon describe themselves as open source, Microsoft's Fluent 2 publishes components for web, iOS, Android and Windows, and shadcn/ui gives you component code to change. You can adopt one as is, or extend it with your own tokens and the components it lacks. Nielsen Norman Group notes that the savings shrink as customization grows. Check each license before you commit.
Sources
- Design Systems 101 · Nielsen Norman Group, 2021
- Design Systems Report 2026 · zeroheight, 2026
- Design Tokens Format Module 2025.10 (Final Community Group Report) · W3C Design Tokens Community Group, 2025
- Design Tokens specification reaches first stable version · W3C Design Tokens Community Group, 2025
- Design Tokens Format Module (Draft Community Group Report) · W3C Design Tokens Community Group, 2026
- Design tokens · Material Design 3 (Google), 2026
- Material Design 3 · Google, 2026
- Human Interface Guidelines · Apple, 2026
- Fluent 2 Design System · Microsoft, 2026
- About Carbon · IBM Carbon Design System, 2026
- U.S. Web Design System (USWDS) · U.S. General Services Administration, 2026
- Design tokens · U.S. Web Design System (USWDS), 2026
- Accessibility · U.S. Web Design System (USWDS), 2026
- GOV.UK Design System · GOV.UK, 2026
- Accessibility · GOV.UK Design System, 2026
- Contribution criteria · GOV.UK Design System, 2026
- Introduction · shadcn/ui, 2026
- Measuring the value of design systems · Figma, 2019
- The Value of Design Systems Study: Developer Efficiency and Design Consistency · Sparkbox, 2021
- Better Code, Fewer Tokens: The Benefits of Code Connect in MCP · Figma, 2026
- What's New in WCAG 2.2 · W3C Web Accessibility Initiative, 2023
Share this article

About the author
Artsiom Yankovich
Co-founder, Head of Design & Strategy
Leads design and strategy, from product logic to brand. 9+ years, 150+ projects.


