Scaling an Enterprise Design System
I led the evolution and ongoing management of an enterprise Design System supporting multiple digital products and product teams.
My role focused on maintaining system consistency, improving scalability, evolving foundations and components, and leading the migration towards Figma Variables to create a more flexible and future-ready design infrastructure.
System Thinking
I worked across foundations, components and product-specific libraries, considering how each change could affect the wider ecosystem. This helped balance shared standards with the specific needs of three different enterprise products.
DesignOps
I managed a structured process for evaluating product needs, testing solutions, releasing updates and keeping documentation aligned. This ensured the Design System could evolve without compromising consistency or introducing unnecessary duplication.
Variables Strategy
I led the transition from legacy styles to a scalable Figma Variables architecture, defining primitive and semantic layers and applying them across the core system. The new structure improved maintainability, cross-component consistency and enabled dark mode support.
Design Leadership
I took ownership of key Design System initiatives while coordinating with design managers and product teams. During the Variables migration, I also mentored another designer, delegating part of the implementation and supporting them until they could contribute independently.
Context
The Design System was already established when I joined, acting as the foundation for multiple enterprise products.
Its structure was built around three main layers: foundations, icons and reusable components. Product teams developed their own libraries on top of the core system, inheriting shared assets while maintaining flexibility for product-specific needs.
As the ecosystem continued to evolve, the main challenge was ensuring the Design System remained consistent, scalable and maintainable while supporting different product requirements.
The goal was not only to maintain a library of components, but to continuously improve a shared design infrastructure used by multiple teams.
My Role
Design System Operations & Governance
Managing an enterprise Design System required a structured approach to evaluating, implementing and communicating changes.
Requests typically originated from product teams through design managers. Each request was analysed to understand its impact across the ecosystem and determine whether it should become part of the core Design System or remain product-specific.
The workflow included:
Requirement discussion with product teams
Internal analysis and design validation
Proposal creation and alignment
Design System implementation
Library release with changelog
Documentation updates when required
This process ensured that new solutions were scalable, consistent and aligned with the needs of multiple products.
Documentation played a central role in adoption. Dedicated Figma documentation files and Confluence pages provided guidance on component usage, anatomy, behaviour, best practices and design recommendations, helping teams use the system effectively and independently.
Evolving the System: Figma Variables Migration
One of the main initiatives I led was the migration of the Design System towards Figma Variables, transforming the existing style-based foundation into a more scalable variable architecture.
The goal was to reduce manual maintenance, improve consistency and create a stronger foundation capable of supporting future requirements, including dark mode management.
I defined the migration strategy, structured the variable architecture, updated foundations and applied the new logic across all core components.
The migration included:
Primitive Variables
52 primitive color variables created through the systematic conversion of legacy color styles
17 primitive measure variables standardising spacing, sizing and layout foundations
Semantic Variables
422 semantic color variables supporting components, states and usage contexts
22 semantic measure variables improving consistency across layouts and interactions
The new variable architecture enabled targeted refinements across existing components, reducing inconsistencies and improving alignment between products and use cases.
Outcome:
A more scalable foundation with improved cross-component coherence and stronger visual governance.
Scaling Across Products
The Design System supported three enterprise products, each with dedicated product libraries built on top of the core system.
Product teams inherited foundations, icons and reusable components from the main library while maintaining flexibility for specific product needs.
Clear guidelines and governance prevented unnecessary duplication while allowing teams to introduce product-specific patterns when required.
This balance helped maintain consistency across the ecosystem while supporting different product contexts.
Impact
Through continuous improvements, structured governance and the transition to a variable-based architecture, the Design System became a stronger foundation for product teams.
Key outcomes:
Supported consistency across 3 enterprise products and 6+ product designers
Improved maintainability through a more scalable foundation architecture
Reduced ambiguity through clearer documentation and usage guidelines
Improved component adoption and designer autonomy
Created a more sustainable workflow for Design System evolution and collaboration
Reflection
Managing an enterprise Design System reinforced my belief that scalability is not only about creating reusable components.
The real challenge is building a system that can continuously evolve through clear principles, strong collaboration and processes that enable teams to move faster without compromising quality.
A successful Design System is not just a collection of assets, it is an ecosystem that connects people, products and decisions.