Enterprise Design Systems: Scale Brands with Consistency and Flexibility 

A Volkswagen Golf and an Audi A3 share more engineering than their different identities might suggest. In 2012, Volkswagen Group introduced MQB, a modular vehicle architecture supporting different models across its brands. By 2022, the group had produced more than 32 million vehicles on that foundation. Shared engineering could scale across a portfolio while leaving room for each brand’s design and character. 

The useful part is where Volkswagen drew the boundaries. Key engineering points stayed fixed, while dimensions such as wheelbase and track width could change. Each model built on shared work, giving teams a tested starting point and room to develop differences their customers cared about. 

That’s how we approach scaling multiple brands within a single enterprise design system. The foundation carries the work every brand needs, while defined options and bespoke work give each brand room to feel like itself. 

Three Tiers of Control 

Brand teams hear “shared design system” and picture every brand pushed into the same buttons, cards and layouts, with a logo swap to tell them apart. A boring, watered-down, one-size-fits-all solution. 

Yet separate builds bring repeated work. Safety information components get rebuilt, contrast checks get repeated, and implementations of approved patterns drift apart. 

Building design systems at an enterprise level shouldn’t mean brands are handcuffed to each other. 

We address this by defining three tiers of control: 

  • Locked: Protected content, required presentation rules and foundational requirements. 

  • Configurable: Supported choices that let teams adapt shared components to their brand and content. 

  • Bespoke: New components or compositions for needs the shared options don’t cover. 

The tiers tell teams what to preserve, what they can adjust and where they can create something new. 

Locked: Protect The Decisions That Matter 

Some decisions should carry through every implementation. Approved claims and copy need protection. Safety information needs the right presentation. Accessibility requirements need to hold as the appearance changes. 

Teams use approved content for the relevant brand, market and context, with changes following the appropriate review process. The system protects that version from casual edits. 

Safety content also follows its own presentation rules. It uses dedicated design settings rather than inheriting the surrounding section’s visual treatment. An expressive page should never make required information harder to find or read. 

A protected content block reduces accidental changes to approved wording and avoidable review cycles. A tested component reduces the need to solve its interaction behavior on every project. Teams gain a dependable starting point, and reviewers can focus more attention on the content and experience in context. 

Configurable: Give Brands Supported Choices 

Most everyday brand expression should be possible through configuration. Teams need enough range to create a distinct experience using components whose behavior is already established. 

That starts with separating visual attributes from component behavior. Palette, typefaces and shapes live in one layer. Another assigns those attributes to roles: an action, a surface or a status message. A button asks for the action color, never for a specific blue. 

We structure our design tokens to accommodate new brands without requiring teams to rebuild the system around them. Each brand can establish its own visual identity while benefiting from the same shared foundation. 

Skins extend those choices across a page. We typically start with four: Neutral, Brand Subtle, Brand and Brand Strong. This provides a flexible baseline that can expand or contract based on the needs of the enterprise. Applied by section, skins let a page open with a bold hero, settle into quieter content and close with a stronger call to action. 

Page templates bring that same balance to the overall experience. They establish consistent placement for required content and essential elements while allowing the surrounding layout, imagery and storytelling to adapt to each brand. Teams can create distinctly different experiences without compromising the structure and requirements that need to remain consistent. 

Small components carry range too. A quick link might be a filled pill for one brand, an underlined editorial link for another and a tall tile for a third. Those options are represented consistently in Figma and code, carrying interaction and accessibility requirements through each variation. 

Bespoke: Make Room For Needs the System Hasn’t Met 

Configuration has limits. Even with flexible components, skins and templates, some brand experiences call for something more distinctive than the shared system can provide. Rather than forcing every creative idea into an existing pattern, an enterprise design system should leave room for intentional departures where they add meaningful value. 

Bespoke components and compositions let brands introduce character and functionality beyond the available options. They should be reserved for key moments where they add clear value, rather than used everywhere by default. Because they extend the system without being fully governed by it, they require additional design, development, testing and maintenance. They still build on the shared foundation: brand roles, accessibility requirements and protected content apply when the design is new. 

Define the need, then check whether an existing component, skin or approved variation can reasonably meet it. If not, weigh the value of a bespoke moment against the cost of creating and maintaining something outside the library. Build and test the new approach with the relevant system owners. Afterwards, decide whether it should remain specific to that brand or become part of the shared library. 

That contribution path helps the enterprise system grow through use, but not every bespoke solution needs to become a standard. A need uncovered by one brand can become a supported option for others, reducing the work required next time, while deliberately local solutions preserve flexibility where the value does not justify broader system investment. 

Why The Range Helps The Enterprise Scale 

Together, the tiers help teams direct effort. Locked elements preserve settled decisions. Configuration handles recurring variation. Bespoke work addresses needs that deserve new design and development. Teams have a route for each kind of work, and the enterprise can invest in shared improvements that benefit multiple brands, markets and channels. 

A shared engineering foundation gives each model a starting point and room for variation. The same principle lets an enterprise add brands without rebuilding every experience from the ground up. Teams reuse what works, configure what varies and contribute new solutions where they’re needed. The investment in each brand can strengthen the foundation for the next. 

The goal isn’t to make every brand drive the same car. It’s to give each one the engineering to go further. 

Next
Next

Beyond the Conversation: Connecting Perspectives, Inspiring Progress