Bloomberg

2025-2026

Modernizing Bloomberg Design System

I helped shape the visual and structural foundations of Bloomberg’s modern design system, turning fragmented product patterns into scalable rules that could support Terminal, Ask Bloomberg, and future AI-driven experiences.

Role

Lead Product Designer

Scope

Design system strategy, foundations, tokens, components, cross-platform alignment

Team

Cross-disciplinary task force across design, engineering, documentation, and library operations

Timeline

2025-2026

Role

Lead Product Designer

Scope

Design system strategy, foundations, tokens, components, cross-platform alignment

Team

Cross-disciplinary task force across design, engineering, documentation, and library operations

Timeline

2025-2026

Context

Modernizing a legacy product without breaking what made it powerful

Bloomberg Terminal had evolved over decades into one of the most complex enterprise products in the financial industry. Its density, speed, and specialized workflows were core to its value—but the same legacy infrastructure made the product difficult to systemize and slow to change.

The Terminal had never operated on top of a fully mature, unified design system. Components, interaction patterns, and visual conventions had accumulated over time across different functions and teams, often shaped by local product needs and technical constraints.

The modernization effort was therefore not simply a visual refresh. The challenge was to modernize the look and feel of the Terminal while building a stronger system underneath it—without disrupting the workflows, density, and infrastructure that existing users depended on.

Current Bloomberg Terminal Function

AskB (Ask Bloomberg) AI powered product, future product direction

Role

Shaping a modern system inside a legacy product ecosystem

I was the lead/sole visual designer on the cross-disciplinary modernization taskforce, working with interaction design, infrastructure engineering, front-end engineering, documentation, and library operations.

My role was to help define how Bloomberg could move from decades of locally evolved UI patterns toward a more coherent system—across foundations, tokens, component architecture, interaction states, and emerging AI patterns—while remaining realistic about the constraints of the existing Terminal infrastructure.

Earlier in the redesign, I also helped guide and organize a broader visual exploration with three other senior visual designers, contributing to the definition of a new Bloomberg product expression before the work moved into system implementation.

Key Decisions

Decisions that shaped the system

Key Decision 1: Build system foundations before scaling modernization

Because the Terminal had not historically been built around a unified system architecture, redesigning individual components alone would only create another layer of inconsistency. I focused on establishing reusable logic across spacing, typography, color, geometry, interaction states, and tokens so that individual redesigns could contribute to a broader system rather than remain isolated improvements.

Trade-off:
The infrastructure could not be rebuilt all at once. The system therefore had to be introduced incrementally—strong enough to create alignment, but flexible enough to coexist with legacy implementation.

Spacing scale and tokens

Corner radius system testing

Key Decision 2: Systemize the most reusable structures first

The redesign started with highly reused components such as Lists, then expanded into Buttons and Menus. The goal was not simply to restyle them, but to define reusable information architecture, slots, hierarchy, states, and composition rules that could work across many Terminal functions.

Trade-off:
Too much standardization would break specialized financial workflows; too little would preserve the fragmentation we were trying to solve.

ListItem IA

Heading system stress test within List component

Key Decision 3: Use Ask Bloomberg to pressure-test the future system

Ask Bloomberg gave us a very different type of product environment—AI responses, documents, charts, tables, financial data, queries, and dynamic follow-up interactions. That made it an important proving ground for whether the emerging system could support not only legacy Terminal workflows, but also Bloomberg’s next generation of experiences.

Trade-off:
AskB needed to move faster than the underlying Terminal system. New patterns had to evolve quickly without becoming a separate visual language.

List component stress testing in AskB

Key Decision 4: Modernize the visual language without fighting the product’s DNA

Bloomberg Terminal could not simply adopt the conventions of modern consumer software. Its density, information hierarchy, speed, and familiarity were fundamental to expert workflows. Studies around spacing, radius, hierarchy, and interaction states helped define where the product could become more modern—and where restraint mattered more than visual novelty.

Trade-off:
The objective was not maximum visual modernization. It was modernization that respected the Terminal’s functional identity and technical reality.

System

From foundations to reusable product architecture

The emerging system connected four layers:

Foundations → Components → Patterns → Product applications

Foundations established the shared visual logic. Components encoded reusable behavior. Patterns combined those components into repeatable workflows. Product teams could then apply and extend the system without starting from scratch. This moved the work away from a collection of UI components and toward a system that could continuously absorb new product needs.

Scale

Proving the system across products and platforms

The emerging system needed to scale beyond individual Terminal/desktop functions. Patterns developed in Ask Bloomberg had to coexist with established workflows, while the underlying foundations also needed to support different platforms.

At the component level, I partnered with the mobile team to align component tokens and semantic structure across desktop and mobile, so the tokens are aligned on the component layer. The values themselves could differ to reflect platform-specific density and interaction needs, but the token logic stayed consistent.

This created an important first step toward a shared cross-platform system: products could preserve their own implementation requirements without drifting into completely separate design languages. The goal was not to align on identical values across platforms. It was shared system meaning with platform-specific expression.

Impact

Creating a path for gradual system adoption across a legacy ecosystem

The modernization work established a clearer path from a historically fragmented UI toward a more coherent and scalable design system. But at Bloomberg’s scale, adoption could never happen as a single migration. The legacy system and the new design system would need to coexist for a significant period of time as products, components, and infrastructure were gradually updated.

A major part of the challenge therefore shifted from defining the system to enabling adoption: helping teams understand when to use the new foundations, how to migrate existing patterns, and how to evolve products without creating a second layer of fragmentation. The long-term goal was not an immediate visual reset, but a controlled transition across the broader Bloomberg ecosystem.

The work created stronger foundations for that transition - clearer system logic, more reusable component architecture, improved designer-engineer alignment, and a more scalable base for both existing Terminal workflows and emerging AI experiences.

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