A design system is a comprehensive, evolving set of design standards. Through reusable components and patterns, it helps teams maintain consistency, reduce duplicate work, and establish a shared design language when designing and developing at scale. It goes beyond color palettes or typography guidelines, typically including style guides, component libraries, pattern libraries, code implementations, and design resources. Content standards can also be included to maintain the quality of both interfaces and text.
Purpose: keeping teams from building separate versions of the same thing
When multiple teams create products or pages independently, the same interface element may be repeatedly designed and coded in different ways. A design system provides shared standards and ready-made components. These help reduce inconsistencies between teams, save time spent on duplicate work, and reduce the amount of code that is difficult to organize.
For example, two departments within a company can use the same set of components to produce consistent results, even without directly collaborating on the design. Developers can refer to and reuse existing implementations rather than starting from scratch each time. This shared language not only helps designers with their work but also makes it easier for design, development, and other departments to collaborate.
What it includes: from usage guidelines to interface implementation
A design system is the overarching framework; a style guide is just one part of it. Common elements include:
- Style guides: Usage guidelines, visual references, and design principles for specific areas such as branding, visuals, or content.
- Component libraries: Documentation of individual reusable interface elements, such as buttons. This covers their appearance, adjustable sizes and text, states such as enabled and disabled, and implementation code.
- Pattern libraries: Documentation of reusable combinations of multiple elements. A page header, for example, might include a title, breadcrumb navigation, search, and primary and secondary buttons.
- Design resources: Ready-to-use design files and assets such as logos, fonts, and icons for designers and developers.
These materials are usually kept together on a website so teams can find and use them easily. However, the boundaries between style guides, component libraries, and pattern libraries can be blurry, and organizations may use these terms differently. Names alone are therefore not a reliable indication of what each includes.
Content guidelines and ongoing maintenance matter too
Design systems often prioritize organizing interface components, but content standards are equally important for producing consistent, high-quality text. For instance, concrete examples of how chatbot messages should and should not be written can help teams decide what to write more quickly.
However, standards cannot fully resolve organizational problems such as having too few content designers or involving them too late. If adding content guidelines directly would overburden product teams, a separate but related content system or style guide is another option. The design system itself still needs ongoing management and updates. When content standards change, the product teams using them should also be notified; creating the documentation is not the end of the work.
Design systems: perspectives from across the web
What can you take stock of before building or expanding a design system?
You can start by creating an asset map: a systematic inventory of existing design assets and components that identifies what is available, what is missing, and what can be reused across channels. This inventory can also help assess the consistency of existing assets, making it useful when building or expanding a design system or component library. The team still needs to decide how to act on the findings.
Does a design system have to be managed by a dedicated team?
Not necessarily. Larger companies with more mature design practices may have a dedicated internal team to oversee, build, and maintain the design system. Smaller companies or those with less mature design practices may have one person responsible for maintenance, usually a more senior team member. Arrangements can vary; what matters is ongoing management and review to keep the system from becoming outdated.
References
- Asset Mapping for Experience Consistencywww.nngroup.com · 2021-03-14T16:00:00+0000 — Discusses: What can you take stock of before building or expanding a design system?
- Content Standards in Design Systemswww.nngroup.com · 2024-05-03T17:00:00+0000 — Source used in the article above.
- Design Systems vs. Style Guideswww.nngroup.com · 2024-05-24T17:00:00+0000 — Discusses: Does a design system have to be managed by a dedicated team?
