# Design System

A design system is a maintained set of principles, guidance, reusable assets, and coded components for producing coherent product experiences.

- Type: framework
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/design-system/>)

## What it means

A design system is shared product infrastructure: it connects design decisions, content guidance, accessibility expectations, reusable interface components, and contribution practices. Unlike a static style guide, it is operated as a living product whose releases and documentation support many delivery teams.

## Why it matters

Without shared infrastructure, teams repeatedly solve the same interface problems and drift in behavior, language, and accessibility. A useful system shortens routine work while making important decisions inspectable, testable, and easier to improve across products.

## When to use it

Use one when several teams build related products, when repeated interface solutions have diverged, or when consistent quality matters across platforms. Start only when there is evidence of recurring needs and capacity to maintain the system.

## How it works

1. Inventory recurring interface decisions and identify user and team needs.
2. Define principles, tokens, content rules, components, and patterns at appropriate levels.
3. Document usage, accessibility behavior, examples, status, and known limitations.
4. Distribute versioned design and code assets through teams’ normal tools.
5. Create contribution, review, release, and deprecation processes.
6. Measure adoption and outcomes, then revise the system from product evidence.

## A practical example

A financial platform finds six differently behaving date fields across three products. Its system team consolidates validated needs into one documented component, provides design and code assets, tests keyboard and screen-reader behavior, and publishes a migration note rather than merely standardizing the color.

## Where it breaks

A design system cannot replace product research, domain expertise, or accessibility testing in context. Centralization can also slow teams or fossilize weak decisions; teams need an exception path, transparent ownership, and evidence-based evolution.

## Common mistakes

- Treating the system as a one-off visual cleanup.
- Counting components rather than measuring product and team outcomes.
- Mandating adoption without support, migration paths, or feedback loops.
- Assuming system components make every implementation accessible.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/design-system/#visualization-design-system>)

## Sources

1. [GOV.UK Design System](<https://design-system.service.gov.uk/>) — Government Digital Service · Institutional design system
2. [U.S. Web Design System](<https://designsystem.digital.gov/>) — U.S. General Services Administration · Institutional design system
3. [Maintaining Design Systems](<https://atomicdesign.bradfrost.com/chapter-5/>) — Brad Frost · Original author

## Related topics

- [Design Tokens](<https://wiki.soroush.uk/topic/design-tokens/>)
- [Component Library](<https://wiki.soroush.uk/topic/component-library/>)
- [Design System Governance](<https://wiki.soroush.uk/topic/design-system-governance/>)
