Bloomberg

2024-2026

Global/Extension Working Model

I created and led a scalable design system operating model that enabled product teams to build reusable solutions, coordinate across teams, and evolve proven patterns into global standards.

Role

Model Creator & Working Group Lead

Scope

Bloomberg UX Design Organization

Team

Cross-product Design Library Managers

Timeline

2024–2026

Role

Model Creator & Working Group Lead

Scope

Bloomberg UX Design Organization

Team

Cross-product Design Library Managers

Timeline

2024–2026

Overview

Scaling a Design System Without Slowing Product Teams

As Bloomberg's product ecosystem evolved, I identified a growing disconnect between the pace of product innovation and the centralized design system contribution process.

Product teams needed to introduce new components and interaction patterns, but getting those solutions into the Global Design System required multiple rounds of review, prioritization, and engineering coordination. The process protected consistency, but it also created bottlenecks and encouraged teams to develop solutions independently.


I proposed a Global–Extension Working Model that balanced centralized standards with distributed product ownership.

After securing UX leadership approval, I introduced the model across the design organization, established its library structure, recruited cross-product contributors, and led the working group responsible for coordinating its adoption and evolution. The result was an operating model that enabled teams to create and reuse product-specific solutions while contributing to a more scalable global design system.

Problem

A Centralized Contribution Process That Could Not Scale

The existing contribution process was intentionally rigorous, but it had become too slow for rapidly evolving product teams. A typical component improvement moved through multiple stages:

Product designer identifies a need → Framework review → Infrastructure engineering intake → Prioritization → Engineering scheduling → Global implementation

Each step made sense independently. Together, they created significant latency. Product teams often needed to iterate within days or weeks, while system-level implementation could take considerably longer. In practice, teams would:

  • build local solutions outside the system

  • duplicate work already happening elsewhere

  • compromise on the product experience

  • or drop proposed improvements altogether

The underlying problem was not component quality. It was the absence of a scalable operating model for distributed contribution.

Model

Creating a Shared Foundation with Product-Specific Extensions

Inspired by Brad Frost's design system recipes concept, I adapted a layered approach to Bloomberg's complex product ecosystem. The model established two complementary levels of ownership.

Global Design System

The Global Design System maintained the shared foundations required for consistency across Bloomberg products:

  • Foundational components

  • Design tokens

  • Accessibility standards

  • Interaction principles

  • Common states and behaviors

  • Broadly reusable patterns

Extension libraries

Extension Libraries enabled product teams to create and maintain reusable solutions tailored to their specific workflows while remaining aligned with the Global Design System:

  • Domain-specific components

  • Emerging interaction patterns

  • Specialized layouts and compositions

  • Reusable solutions shared across related product functions

  • Components with potential for future global standardization

The central principle was to standardize what should be shared globally, while allowing domain-specific solutions to remain closer to the teams that understood them best.

Extensions also provided a pathway for emerging patterns to mature through product usage and cross-team collaboration before being considered for global adoption.

Operations

Turning the Model into an Operational System

Defining the architecture was only the beginning. To make the Global–Extension Model sustainable, I established the ownership structure, component discovery tools, and cross-team governance needed to support distributed contributions.

Distributed Ownership Across Seven Extension Libraries

I coordinated the establishment of seven Extension Libraries across Bloomberg's product ecosystem: AI Pattern, AskB, Core Products, Employee Productivity, Enterprise Products, Framework, and Quant & Analytics. Each library had designated managers and contributors responsible for maintaining reusable components and patterns within their product area.

This distributed structure allowed teams to address specialized product needs while remaining aligned with the Global Design System. It also established clearer ownership and reduced reliance on a centralized team for every product-specific design decision.

Seven Extension Libraries with designated ownership across Bloomberg product areas. Reconstructed from the original library structure.

Centralized Component Discovery

To improve visibility across Extension Libraries, I created a centralized component tracker in Google Sheets. Each library had a dedicated tab documenting its managers, components, status, owners, and notes. This provided a shared view of work across product areas and made it easier to identify existing solutions before creating new ones. The tracker also helped surface overlapping component needs, creating opportunities for collaboration and reuse across teams.

Centralized component tracker documenting ownership, development status, and reusable components across Extension Libraries. Reconstructed from the original tracking workflow.

Cross-team Governance

I formed and led a cross-product working group to coordinate contributions, review emerging patterns, and identify opportunities for global standardization. The group initially met weekly, later transitioning to a monthly cadence as the model matured. I recruited contributors, facilitated design reviews, connected teams with overlapping requirements, and helped establish alignment between Extension Libraries and the Global Design System.

Rather than requiring every new component to enter the Global System immediately, the model allowed patterns to mature within their product domains. Components with broader applicability could then be evaluated collaboratively for global adoption. This created a more structured path from product-specific innovation to shared design standards.

Reuse in Practice — Trading Blotter

Trading workflows rely on complex, domain-specific interfaces that appear across multiple functions. Trading Blotters are one example, combining dense market data, trade details, dealer information, status indicators, and execution controls. These patterns require consistency within the trading domain, but their specialized behavior does not necessarily belong in the Global Design System.

The Trading Blotter demonstrated a key principle of the model: not every reusable component needed to become global. Some components delivered the greatest value by remaining standardized within their specialized product domain.

Example of a complex trading interface illustrating the need for domain-specific component reuse across Terminal Enterprise trading functions.

Evolution

Evolving Product-Specific Patterns into Global Standards

One of the most important principles of the model was that the boundary between extension and global was not permanent. A pattern could begin as a local product need, mature through extension usage, and later become a candidate for the global system. This created a new path:

Product need → Extension proposal → Cross-team review → Shared implementation → Real product usage → Global candidate

Rather than asking whether a component might be useful globally, we could evaluate it based on actual usage across teams. Below provided 2 examples of extension graduate to global process.

Global Tile — From Fragmented Patterns to a Published Component

Across Bloomberg Terminal, teams were developing different tile and card components for use cases ranging from News to Enterprise dashboards. Although their content and workflows varied, these components shared underlying structural and interaction requirements. At the time, the Global Design System did not provide a standardized Tile component.

I led a cross-product working group to consolidate these requirements, align teams around common design principles, and define a scalable component architecture. The work required distinguishing globally reusable patterns—such as shared structure, content hierarchy, title and subtitle treatments, and common menu behaviors—from configurations that needed to remain specific to individual product areas.

The initiative resulted in a Global Tile component published to the Global Design System Library, together with supporting documentation.

This demonstrated the complete evolution pathway: fragmented product needs became visible through cross-team collaboration, were translated into shared standards, and ultimately became reusable global infrastructure.

Badge — Identifying a Global Component Candidate

The Employee Productivity team identified a custom Badge component used in BNEW<GO> to communicate announcement metadata, categories, and status through color, text, and icons. Although originally designed for a specific product experience, the pattern addressed a broader interface need shared by multiple product areas.

Through the Extension Model, components like Badge could be surfaced, reviewed, and evaluated for potential adoption into the Global Design System. This illustrated how product-specific solutions could become candidates for broader standardization without requiring immediate global implementation.

Badge component identified by the Employee Productivity team as a high-potential candidate for global standardization.

Impact

Building a Design System That Could Evolve Through Its Teams

The Global–Extension Working Model introduced a more scalable way for Bloomberg's product teams to contribute to the design system while maintaining shared standards. The work established several concrete outcomes:

  • Seven extension libraries supporting distributed ownership of product-specific reusable components and patterns.

  • A centralized component inventory that improved visibility across libraries and helped teams identify opportunities for reuse.

  • A cross-product governance process that brought teams together to evaluate overlapping requirements and coordinate shared design decisions.

  • Reusable domain-specific components, including the Enterprise Dealer Panel, that supported consistency within specialized workflows.

  • A published Global Tile component and documentation, demonstrating how emerging product patterns could evolve into global standards.

Together, these outcomes shifted the design system from a predominantly centralized contribution process toward a model that supported distributed innovation with shared governance.

The most important lesson was that scaling a design system required more than expanding its component library. It required designing the organizational structures, discovery mechanisms, and decision-making processes that allowed the system to evolve sustainably.

A scalable design system is not simply a collection of reusable components. It is an operating model that enables teams to create, discover, share, and standardize them.

Senior product designer specializing in scalable design systems, platform foundations, and visual UX for complex digital products.

HanZhangDesign © 2026 by Han Zhang

Contact

endorahan@gmail.com

Senior product designer specializing in scalable design systems, platform foundations, and visual UX for complex digital products.

HanZhangDesign © 2026 by Han Zhang

Contact

endorahan@gmail.com

Senior product designer specializing in scalable design systems, platform foundations, and visual UX for complex digital products.

HanZhangDesign © 2026 by Han Zhang

Contact

endorahan@gmail.com