esc
  • WorkflowsPages
  • Case studiesPages
  • Machine Learning FoundationsLearn
  • AI EngineeringLearn
  • AI Guardrails & Red TeamingLearn
  • UI/UXLearn
  • Design SystemsLearn
  • Production System DesignLearn
  • Book a callContact
  • Download ResumeContact
Let’s talk

I’ll build the agent for it.

Need of Design System: Why Teams Build Shared Parts and Rules

A design system is a shared toolkit of parts and rules. Learn the problems it solves, the five needs it meets, and the costs teams must plan for.

In short

Teams build a design system, a shared toolkit of parts and rules, to solve the problem of inconsistent work, and it meets five needs including speed and consistency.

10 min readFree

What you will learn

Picture a company with a shopping app, a website, and a help center. Each one needs buttons, forms, and menus. Who decides how a button looks? Who checks that a new screen matches the old ones? A design system is one common answer. This lesson explains what it is, why teams need one, and what it costs.

The lesson takes about 10 minutes to read. Learn the key words first, because the later sections use them.

Key words

Design system
A shared set of reusable parts, written rules, and guides that a team uses to design its products.
Component
One reusable piece of a screen, such as a button, a card, or a text field.
Pattern
A group of components that work together to solve one common job, such as a search bar with filters.
Style guide
A document with rules for the look and voice of a product, such as colors, fonts, logos, and wording.
At scale
Working on many screens, products, or teams at the same time.
Redundancy
Doing the same work more than once, such as rebuilding a part that already exists.
Consistency
Parts of a product that look and behave the same way wherever they appear.
Single source of truth
One trusted place where the current version of a part or rule is kept.

What is a design system?

A useful way to think about a design system is a rulebook plus a parts bin for screens. Nielsen Norman Group, a research firm known for usability work, describes it as a set of standards for managing design when many screens must be made. The standards rely on reusable parts, and their purpose is to cut duplicate effort and keep the visual style steady across every channel a company uses.

A design system is not one single file. It is made of smaller pieces that work together. Nielsen Norman Group treats style guides, component libraries, and pattern libraries as parts inside the larger system. The larger system is the parent, and the smaller pieces are its children.

  • Style guide

    The rules for look and voice. It covers colors, typefaces, logos, and how writing should sound.

  • Component library

    A shelf of ready-made parts, such as a button, with the sizes and states each part can take.

  • Pattern library

    Groups of parts that solve one job together, such as a page header that holds a title, a search box, and buttons.

Tip

A design system needs a home that everyone can reach, usually a website plus a shared design file. If a rule lives only in one person's head, it is not part of the system yet.

What problem does it solve?

Without a shared system, each team tends to build its own version of the same thing. A large organization can end up with several slightly different buttons, each one coded again by a different developer. Nielsen Norman Group says this pattern leads to three problems: the product looks uneven, time gets wasted, and the code becomes hard to manage.

The problem grows with size. Nielsen Norman Group says large organizations end up with multiple versions of the same element. In the arXiv study, nine leaders of design systems were interviewed. They said teams should not have to rebuild basic parts for every new project.

  • Repeated parts

    Different people rebuild the same button, form, or header because nobody knows the part already exists.

  • Drifting screens

    Two products from the same company look like they were made by different teams.

  • Slow handoffs

    Nielsen Norman Group says time gets wasted when the same work is repeated.

What are the five reasons teams need one?

The guidance and research point to five main needs. Each one has its own short sub-section below.

Speed: build from parts that already exist

The most common payoff is speed. Nielsen Norman Group calls this the primary benefit: a team can reuse premade components and elements, so it does not start from zero on every screen. The leaders in the arXiv study described a similar effect. One said a team can move from a rough idea to a full prototype much faster when the parts are already there.

Speed also has a second side. When one central set of parts exists, each new screen needs fewer fresh decisions. A choice made once can stand for everyone, so the next team does not have to make it again.

Consistency: the same look and behavior everywhere

Consistency is the second need. In the arXiv study, five of the nine leaders named consistency and coherence as a main benefit. Their point was simple: when a system is used, each component keeps the same design and the same working method across several products. A button should look and act the same in the app, on the website, and in the help center.

Consistency covers behavior, not only color. The arXiv researchers found that open-source design-system discussions focused more on how parts behave, such as what happens on hover, focus, or when disabled, than on how they look. Nielsen Norman Group adds that a shared source of parts keeps separate departments visually linked, even when they work on different products.

Shared language: one word, one meaning

A design system gives a team shared words. Nielsen Norman Group uses the dropdown menu as an example. If the system defines one element with that name, nobody needs to debate what a dropdown should do. The same guidance says this matters most when people change roles or work in different places.

The arXiv study heard a similar point. One leader described how a designer can ask a developer for a primary button, and both people picture the same thing. That shared picture means both people are thinking of the same thing.

Onboarding: new people learn faster

New designers and developers must learn how a company builds things. A written design system acts as a guide they can read on their own. Nielsen Norman Group describes it as an educational tool for junior designers and content writers, and as a reminder for experienced staff too.

The arXiv study found that leaders valued this. They said newcomers can easily join a team when it changes and understand how the work runs.

Focus: designers solve harder problems

When simple parts are already built and reusable, designers spend less time on small visual tweaks. They can give more attention to harder questions, such as what information should come first on a page or how a person moves through a long task. Nielsen Norman Group notes that this benefit may look small for a few screens, but it becomes large when dozens of teams and thousands of screens are involved.

How does a team start a design system?

Teams rarely start by writing a huge rulebook. The arXiv study describes a bottom-up approach: take parts that have already proven useful in real products, make them general, and share them back out. The steps below follow that idea.

  1. 1

    Collect what exists

    Gather screens from every product. Write down each button, form, header, and menu that appears more than once.

  2. 2

    Pick the most repeated parts

    Start with the basics that appear most often, such as buttons, text fields, and page headers. Skip rare parts for now.

  3. 3

    Agree on one version

    Compare the different versions people built. Choose the best one, then decide how it looks and acts in each state, such as hover, focus, and disabled.

  4. 4

    Write down the rules

    For each part, say when to use it, when not to use it, and show a short example. Keep the wording plain.

  5. 5

    Name owners and collect feedback

    Give a small team the job of keeping the system current. Let the people who use it report problems and ask for changes.

Tip

Start small. A design system does not need to be huge on day one.

Real examples you can look up

You can study public design systems to see the need in practice. Each one below is a real, named system. Use them as a starting point for your own research.

  • Material Design (Google)

    Google's design system. The arXiv study notes it is used across several Google products, including Gmail, YouTube, and Google Drive, and that outside developers also adapt it for their own products.

  • GOV.UK design system

    A public, open-source design system. It was one of the 41 open-source design systems the arXiv research team studied.

  • Shopify Polaris

    Shopify's design system. The arXiv study says the Shopify brand is built into its color schemes, component styles, and workflows, so the apps on the platform feel like one experience.

  • IBM Carbon

    IBM's design system. Nielsen Norman Group names it alongside Material Design as an example of a design system.

Tip

When you study a system, ask three questions: What parts repeat? Which rules are written down? Who keeps the system up to date?

What are the costs and limits?

A design system is useful, but it is not free. Nielsen Norman Group lists several hurdles that can stop a team from using one well. Know them before you start.

  • Time and people

    Building and keeping a system takes time and a dedicated team. It is never finished, because it changes as teams send feedback.

  • Teaching

    People need instructions for using the system. Without them, parts may be applied wrongly or unevenly across screens and teams.

  • Wrong expectations

    Some people see each project as a one-off that needs no shared parts. This view can hide a chance to save effort.

The arXiv research found that teams often struggle to balance customization and standardization. A product team may need a part the system does not yet have. Should the system add it, or should the team build its own? The leaders said this debate is hard, and that it can make the system feel like a limit.

What is the tension between rules and freedom?

Six of the nine leaders in the arXiv study named balancing customization and standardization as a major challenge. One leader said people thought the design system was limiting them, and that a large communication effort was needed to explain that it offers rules and help. Plan for this conversation from the start, not after people complain.

Tip

Present a design system as help, not policing. For each rule, share the reason behind it.

Check your understanding

Quick check

According to this lesson, what is the main job of a design system?

Quick check

Which of these is a real cost or limit of a design system?

Key takeaways

  • The need

    Without shared parts and rules, teams repeat work and their products drift apart.

  • The payoff

    A system brings speed, consistency, a shared language, faster onboarding, and more time for hard design problems.

  • The price

    A system needs time, a team to own it, clear instructions, and a plan for the tension between rules and freedom.

Sources

How is this lesson?

Last updated on 17 November 2026

Learn with me

Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.