Skip to main content
Published in Product Insights

Design Systems: What They Are and Why You Need One

Design Systems: What They Are and Why You Need One
Table of contents
  1. What Is Inside a Design System?
  2. When Is a Design System Worth Building?
  3. Why Do Design Systems Matter More When AI Writes Code?
  4. Who Maintains a Design System?

By definition a design system is a complete set of standards intended to manage design at scale using reusable components and patterns. When properly implemented, a design system provides a lot of benefits not only to design teams but development teams as well.

Imagine you are tasked with baking a cake. You know what it looks like from the outside and from your extensive experience eating cakes you know that cakes have layers, frosting and, sometimes, decorations. But do you know just from looking at it what ingredients were used to make it? To successfully make your cake you will need to know more than just the experience of eating cake. You need to know the ingredients and how to use them. Creating a design system is a lot like creating a recipe.

Taking this very relatable scenario one step further, you are now a cake baking superstar. Customers love you, you're getting very busy and you need to hire staff. As you look to expand your cake baking enterprise you know you want scalability, consistency, to maintain productivity, and to share your cake knowledge with the new bakers so they can follow the recipes. So what do you do? You create a recipe book.

In designing digital products, as in establishing your very own cake shop, the overarching goal is to be able to build for scale. Having to produce digital products (or cakes) without any clear guidance on how to do it isn't very helpful.

When creating a design system one method that I like to reference is Brad Frost's Atomic Design. Atomic design is a methodology composed of five distinct stages working together to create interface design systems in a more deliberate and hierarchical manner. Frost defines the five stages of Atomic Design as:

  1. Atoms: The foundational building blocks that comprise all user interfaces. "Atoms" include basic HTML elements like form labels, inputs, buttons, colors, fonts and others that can't be broken down any further without ceasing to be functional.
  2. Molecules: In interfaces, molecules are relatively simple groups of UI elements functioning together as a unit. For example, a form label, search input, and button can join together to create a search form molecule. Creating simple components helps UI designers and developers do one thing and do it well. Burdening a single pattern with too much complexity makes software unwieldy. Therefore, creating simple UI molecules makes testing easier, encourages reusability, and promotes consistency throughout the interface.
  3. Organisms: Organisms are relatively complex UI components composed of groups of molecules and/or atoms and/or other organisms. These organisms form distinct sections of an interface.
  4. Templates: Page-level objects that place components into a layout and articulate the design's underlying content structure.
  5. Pages: Specific instances of templates that show what a UI looks like with real representative content in place.

The Atomic Design method is not a linear process, but rather a mental model to help us think of user interfaces as both a cohesive whole and a collection of parts at the same time. While this method is appropriate for designing and developing evergreen design systems for digital products, there are plenty of other existing design systems that designers often use such as:

  1. Google Material Design
  2. Shopify Design System Polaris
  3. Apple Human Interface Guidelines

So far, we've primarily focused on the methods of understanding the value of creating and following a design system for digital products, but the practice of design systems also extends to how a brand is expressed through other communication touchpoints. Similar to design systems for digital products, designers create traditional "Brand Guides" which focus on the overall strategy and consistency of a brand as it relates to a logo, colors, and brand personality, which include visual examples of how the brand should be executed in various communications.

It's been common practice to create brand guidelines ahead of website design in order to ensure that the brand look and feel is in place first. The problem is that these brand guidelines often don't include guidance for digital products. With the digitization of work, products, and communication, this is now changing.

The practice of creating Design Systems for digital products is still relatively new and rapidly evolving. In 2005, Jenifer Tidwell published her book Designing Interfaces followed by Yahoo! publishing their open source Yahoo User Interface Library (YUI) in 2006. In 2008, phrases such as "CSS Libraries", and "pattern portfolios" paved the way for the creation of "Front End Style Guides" and "Style Tiles". In 2011, Twitter shared their own open-source framework around design patterns, Blueprint (later renamed Bootstrap), and Google's Material Design followed in 2014.

Since then we've seen design systems from IBM, AirBnb, and Uber that encompass not just their brand guidelines, but also full-scale design systems.

Whether you're a small design team or a large enterprise business, defining, scaling and streamlining your design ensures a more holistic user experience, saves money and prepares you for the future. To quote former IBM president Thomas J. Watson Jr., "Good design is good business", and there is no easier way to bring value to your business than establishing a strong design system.

When developing design systems at The Gnar, we take a holistic approach to ensure that all aspects of your unique brand seamlessly integrate into your digital experiences. From website content to software error messages, each touchpoint with your customer is an opportunity to reinforce your brand values alongside a consistent look and feel.

What Is Inside a Design System?#

A design system has "two important parts": the design repository and the people who manage it, says Nielsen Norman Group's guide Design Systems 101, last reviewed in August 2026. It says the repository will "often contain" a style guide, a component library and a pattern library.

In Gnar's case study for the Massachusetts Disabled Persons Protection Commission (DPPC), the team "created a unified design system and component library" for the new platform. The table below lists the parts in the guide's own words.

PartWhat the guide saysExamples the guide names
Style guideThe "most-common style guides tend to focus on branding," such as colors, typography, trademarks, logos and print media. But "style guides also offer guidance on content," such as tone of voice and language recommendations.The 1976 NASA Graphics Standards Manual and Mailchimp's Content Style Guide.
Component libraryHolds "predetermined, reusable UI elements," each with a component name, description, attributes, state and code snippets.The component libraries of Google's Material Design and IBM's Carbon.
Pattern libraryHas "collections of UI-element groupings or layouts," while component libraries specify individual UI elements.Reusable patterns in the Atlassian design system and page templates in the US Web Design System.
The peopleThe people who manage it. At a minimum, 1 interaction designer, 1 visual designer and 1 developer.Covered in the section on who maintains a design system, below.

A design token is "information associated with a human readable name, at minimum a name/value pair," says the Design Tokens Specification. Its example is color-text-primary: #000000. This post's Atomic Design list puts "colors, fonts" among the atoms. A token is where a value like that gets a name.

Material Design's design tokens overview says "Design tokens are the building blocks" of all UI elements. It adds that the same tokens are used in designs, tools and code.

Uber's April 2019 post on Base Web puts tokens inside its definition of a design system. It says reusable components, "in combination with a set of rules and design tokens," store visual design information such as colors or spacing.

The Design Tokens Community Group is a W3C Community Group. On October 28, 2025, it announced the first stable version of its Design Tokens Specification, 2025.10. The announcement names "reference implementations in leading tools" including Style Dictionary, Tokens Studio and Terrazzo.

When Is a Design System Worth Building?#

"Design systems are best when the company foresees years of future, replicable design work," says Nielsen Norman Group's guide. For a prototype likely to change, it says a full system is "probably not going to generate a desirable ROI" in the near term.

The same guide names three ways to get one. The table gives its words on each.

ApproachWhat the guide says
Adopt an existing systemUsing an existing design system is "the lowest-cost approach," it says.
Adapt an existing systemThe cost savings from the existing system "will diminish" as customizations and adjustments increase. In the long run, you "may be better off creating your own design system anyway," it says.
Create your ownA custom system "will be worth it if the organization has particular needs" that open-source design systems cannot meet.

Brad Frost covers timing in chapter 4 of Atomic Design. Design systems and their pattern libraries are "often created in conjunction with" a new design or redesign project, replatforming effort, or other initiative.

The same DPPC Abuser Registry case study describes a design system made during a new platform project. The work "kicked off with a Discovery and Design phase," it says, in close collaboration with the DPPC team. The goal of its design system was to "keep the entire design and development team on the same page" during design hand-off. The case study also says the goal was to "maintain consistency in product" while designing in sprints.

The Gnar Company's UI/UX design page puts design systems in its Build phase. That phase "builds component-based UI architectures for scalability," the page says.

Why Do Design Systems Matter More When AI Writes Code?#

Component libraries with clear specifications "allow agentic systems to implement consistent UI at scale," says The Gnar Company's post on how product management and design roles change in agentic development. A one-off screen design "gets interpreted differently each time," while a "well-documented button component gets implemented correctly a thousand times," the post says.

IBM's Carbon site, read November 16, 2026, describes Carbon MCP. It says Carbon MCP connects "AI applications directly to the design system" with real-time access to components, tokens, icons, guidance and code.

Who Maintains a Design System?#

Nielsen Norman Group's guide says the team should include "at a minimum" 1 interaction designer, 1 visual designer and 1 developer. Ideally, it adds, the team should also include a part-time researcher, a part-time architect and a content writer. That applies "if these roles are explicitly determined" in your organization.

The DPPC case study lists the team that built that platform and its design system: "a product manager, product designer, three software engineers, and an AWS infrastructure engineer".

Brad Frost splits the work in chapter 5 of Atomic Design. The design system makers "create, maintain, and govern the system," he writes. The users are "the teams across the organization" who will take the system and employ its interface patterns to specific applications.

He also quotes Nathan Curtis, who calls a style guide "an artifact of design process" and a design system "a living, funded product" with a roadmap and backlog.

Frost says a solid governance strategy "starts by answering some important questions about handling change." His nine questions follow, word for word.

  • What happens when an existing pattern doesn't quite work for a specific application? Does the pattern get modified? Do you recommend using a different pattern? Does a new pattern need creating?
  • How are new pattern requests handled?
  • How are old patterns retired?
  • What happens when bugs are found?
  • Who approves changes to the design system?
  • Who is responsible for keeping documentation up to date?
  • Who actually makes changes to the system's UI patterns?
  • How are design system changes deployed to live applications?
  • How will people find out about changes?

After establishing your design system, the work doesn't end there. Technology is rapidly evolving and so are the needs of your users. Thinking back to our super star baker, the original cake that won over customers years ago may not be as good as it is today, or perhaps you've added a lot of new desserts as a result of customer requests and the products are longer as consistent as they once were.

In my next post, I will break down why it's important to reevaluate your current design system in order to see what is and isn't working through an analysis commonly referred to as a "Design Audit".

Learn more about how The Gnar builds design systems.

Frequently asked questions

What are the smallest parts of an Atomic Design system?

Atoms are basic elements such as labels, inputs, buttons, colors and fonts. Molecules combine elements into a working unit, such as a search form.

How do brand guides differ from digital design systems?

Brand guides focus on brand strategy and consistency, including logos, colors and personality. They often do not include guidance for digital products.

How does Gnar approach design systems?

Gnar integrates the brand into digital experiences. Website content and software error messages are both opportunities to reinforce brand values and a consistent look and feel.

What is the difference between a design system and a style guide?

A style guide is often one part of a design system. Nielsen Norman Group says the most common style guides "tend to focus on branding" and also cover content. A design system adds component and pattern libraries and the people who manage it. Brad Frost quotes Nathan Curtis calling a style guide "an artifact of design process."

What are design tokens?

The Design Tokens Specification defines a design token as "information associated with a human readable name, at minimum a name/value pair." Material Design says "Design tokens are the building blocks" of all UI elements. The W3C Design Tokens Community Group announced its first stable specification, 2025.10, on October 28, 2025.

When is a design system not worth building?

For a prototype that is likely to change, Nielsen Norman Group says a full system is "probably not going to generate a desirable ROI" in the near term. It says design systems are best when a company foresees "years of future, replicable design work" ahead.

Who maintains a design system?

Nielsen Norman Group says the team should include "at a minimum" 1 interaction designer, 1 visual designer and 1 developer. Brad Frost says the makers "create, maintain, and govern the system." The users are the teams across the organization who apply its interface patterns to specific applications.

Stay In The Loop

Never miss an update. Get the latest blogs, webinars, and expert insights straight to your inbox from The Gnar.