Loading

StudioBy Bait · · 11 min read

Design system: what it is and how to structure one for multi-brand groups

A design system is the set of components, tokens, documentation and governance that guides digital products. See how to structure one for multi-brand groups.

Modular glass and ceramic blocks forming three related compositions.

A design system is the set of reusable components, design tokens, patterns, documentation and governance rules that an organization uses to design and build digital products consistently. It brings design and code decisions together in a single source: how a button behaves, which color indicates an error, how a form validates a field and who can change each of these answers.

In large companies, the same interface is rebuilt many times. Different teams solve error states, navigation, tables and accessibility in parallel, each with its own cost and its own defects. In groups with several brands, the problem multiplies: each brand has a website, an app, a customer portal and logged-in areas. A design system reduces this duplication and, when well designed, preserves what sets each brand apart.

What a design system is, in practice

A design system is not a file. It is an internal product, with users (designers, developers, writers and product teams), versions and owners. It is usually organized in four layers.

  • Foundations: color, typography, spacing, grid, icons, motion and voice, expressed as design tokens.
  • Components: buttons, fields, menus, tables, modals and cards, with states, variants and usage rules, implemented in code and mirrored in the design tool.
  • Patterns: solutions for recurring tasks that combine components, such as sign-up, search, filtering, checkout or error messages.
  • Documentation and governance: when to use each piece, examples, accessibility criteria, the contribution process and version history.

The library in the design tool is one of this system's interfaces. The code package is another. The system exists when both deal with the same decisions, under the same names, and when someone is responsible for keeping them aligned.

Design tokens: design decisions in a format tools can read

Design tokens are design decisions stored as name and value pairs, in a format that design and code tools can read. Instead of repeating a color's hexadecimal code on every screen, the product uses a name, such as color.text.primary, and the value is defined in a single place. When the value changes, it changes on every surface that uses the token.

Tokens are usually organized in levels. Primitive tokens describe the available palette: a specific blue, a font size. Semantic tokens describe function: primary text, primary action, raised surface, error border. Components consume the semantic tokens, not the primitive ones. It is this intermediate layer that allows the same library to dress different brands.

There is a public effort to standardize this format. The Design Tokens Community Group, a W3C community group, published in October 2025 the first stable version of the Design Tokens Format Module, which defines tokens in JSON, with groups and references between tokens. The document itself clarifies that it is not an official W3C standard, but it offers a neutral basis for exchanging tokens between tools.

Governance: who maintains it, how to contribute and how to version it

Many of the design systems that lose relevance do not fail for lack of components. They fail for lack of an owner. Governance answers three questions.

Who maintains it. A dedicated central team takes care of the foundations, the shared components, the documentation and the release of versions. In multi-brand groups, each brand or unit appoints a focal point, who brings local needs to the central team and tracks adoption internally. Executive sponsorship and a dedicated budget keep the system from depending on the goodwill of each project.

How to contribute. Product teams will find needs that the system does not yet cover. The process needs to say how to propose something new, who evaluates it and against which criteria. The GOV.UK Design System contribution criteria are a useful public reference. At the proposal stage, the component needs to show that it serves several teams and does not duplicate something that already exists. Before publication, it needs to have been tested with users, including people with disabilities, be consistent with what already exists and be versatile enough for different contexts.

How to version it. The component package should follow a versioning rule known to everyone. Semantic versioning, for example, separates compatible fixes (patch), compatible new features (minor) and changes that break current usage (major). Every breaking change needs to come with a migration note, a deadline and, when possible, a period in which versions coexist.

Design system, style guide and brandbook: what is the difference

The three terms appear together and are frequently confused.

  • Brandbook, or brand manual: defines the identity and use of the brand across all media, from the logo to the voice, including print pieces, physical spaces and campaigns. It is the topic of the article on brand manuals and brandbooks.
  • Style guide: documents visual and editorial rules, such as palette, typography, tone of voice and spelling. It can be part of the brandbook or a separate guide. It describes rules, but does not deliver ready-made pieces for building products.
  • Design system: translates part of these decisions into usable form for digital products, with tokens, components implemented in code, interaction patterns and a maintenance process.

The brandbook says who the brand is and how it presents itself. The design system makes these decisions work across hundreds of screens, with accessibility, error states and performance. One does not replace the other, and the design system should consume the brandbook's decisions, not reinvent them.

When a group needs a shared system with several themes

For a group with several brands, the question is not whether each brand will have its own design system, but what should be shared. The answer starts with the brand architecture. Endorsed brands or brands with a common promise tend to share more. Independent brands, in distinct categories, share less expression, but can still share behavior.

A useful model separates three layers. Structure defines how components are organized. Behavior deals with interaction, focus, validation and states. Expression brings together typography, colors, shapes, motion and language. Structure and behavior are usually shareable across brands. Expression becomes a theme.

A multi-theme system uses the same component library and swaps the set of semantic tokens according to the brand. There is only one button; the primary action color, the border radius and the typography come from each brand's theme. This arrangement makes sense when these signs appear:

  • Several brands maintain digital products with similar flows, such as sign-up, customer area, search or checkout.
  • The brands share a technology platform, CMS or development teams.
  • There are common accessibility, security or compliance requirements that are currently solved several times over.
  • The group plans acquisitions and wants to integrate new brands without rebuilding the interface foundation.

The arrangement makes less sense when a brand needs very different interaction patterns for business reasons, or when the technology of each operation is so different that the integration cost outweighs the gain. In these cases, sharing tokens, accessibility criteria and documentation already reduces duplication, even without a common code library.

How to implement it without starting from the catalog

  • Map each brand's digital properties, the technologies used and the flows that repeat most often.
  • Choose a flow common to two different brands, with high usage and a visible maintenance cost.
  • Define the semantic tokens needed for this flow and create one theme per brand.
  • Build the flow's components once, with states, accessibility and documentation.
  • Put the result into production at both brands and measure the effort before expanding the catalog.
  • Publish the contribution process and the versioning rule before opening the system to other teams.

Hypothetical example: three brands, one sign-up flow

Consider a hypothetical group with three financial services brands, each with its own website and app. The figures below are illustrative and do not represent market or client data. Today, each brand maintains its own sign-up flow, with 12 components each: that is 36 components to solve the same problem. An accessibility defect fixed in one brand remains present in the other two.

With a shared system, the group builds 14 components: the 12 of the common flow plus 2 for an additional verification step that one of the brands requires for business reasons. Each brand receives a theme with its tokens. The number of components to maintain drops from 36 to 14, and a fix published in the system reaches all three brands in the next update. The additional step exists as a capability built into the system, not as a permanent copy of the component, which keeps one of the brands from going back to maintaining its own version.

How to measure adoption and return

Measuring a design system by the number of components published leads to wrong decisions. Useful indicators look at usage and effect.

  • Adoption: the share of active products that use the system package and the share of screens built with system components rather than local components.
  • Version lag: how many versions behind the current one each product is. High lag indicates difficult updates or too many breaking changes.
  • Efficiency: time to implement similar flows before and after the system, taking into account the complexity of each one.
  • Quality: recurring interface and accessibility defects per product.
  • Contribution: proposals received from product teams and the central team's response time.

Include accessibility in each component's acceptance criteria. WCAG 2.2 offers testable criteria, but using an accessible library does not guarantee that each final page meets them: content, composition and integrations also need to be checked. The article on performance, accessibility and conversion covers this verification.

Common design system mistakes

  • Treating the design system as a project with a delivery date, rather than as a product with an ongoing team and budget.
  • Starting with the complete catalog instead of the flows that repeat most often.
  • Keeping the design library and the code separate, with different names and versions.
  • Using primitive tokens directly in components, which prevents creating themes per brand.
  • Standardizing the expression of brands that exist precisely because they are different.
  • Publishing breaking changes without a migration note or a deadline.
  • Measuring success by the number of components rather than by usage in production.

Frequently asked questions about design systems

What is a design system, in a few words?

It is the set of components, design tokens, patterns, documentation and governance rules that an organization uses to build digital products consistently. It connects design and code decisions in a single source. It is maintained by a responsible team and released in versions.

Is a design system the same as a Figma library?

No. The library in the design tool is one of the system's interfaces. Without components implemented in code, documentation and a maintenance process, the library becomes a visual reference that each team reinterprets in its own way.

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

A style guide documents visual and editorial rules, such as colors, typography and tone of voice. A design system includes these rules, but delivers them in usable form for digital products: tokens, components in code, interaction patterns and a process for evolving them.

What are design tokens?

They are design decisions, such as colors, sizes and spacing, stored as name and value pairs in a format that design and code tools can read. They make it possible to change a value in one place and propagate the change to every product. Semantic tokens, which describe function, are the basis for creating themes per brand.

Does a group with several brands need a design system for each one?

Not always. When the brands have similar digital flows and share technology, a system with a common library and one theme per brand usually reduces duplication without erasing each brand's identity. Brands with very different interaction patterns can share tokens, accessibility criteria and documentation, without a common code library.

How long does it take to create a design system?

There is no universal timeline: it depends on the number of brands, products and technologies involved. The safest path is to put a first shared flow into production, measure the effort and expand from there. As a product, the system has no end date, because it evolves along with the products it serves.

To turn identity into shared digital infrastructure, explore our design systems area and see how to organize a multi-brand website architecture.