CASE STUDY | BX DESIGN SYSTEM

The Blackstone
Digital Experience.

A GLIMPSE INTO SOME OF MY DESIGN WORK WITHIN THE BX DESIGN SYSTEM. COMPONENTS, TOKENS, & GRID BEHAVIOR USED ACROSS BLACKSTONE’S DIGITAL ECOSYSTEM.

Visit Blackstone.com
Blackstone digital experience hero composition

Role

Product Designer
(UX Design Consultant)

Client

Blackstone
New York, NY

Timeline

September 2022
– March 2023

Team

2x Product Designers (UI/UX)
1x Visualization Engineer

Surfaces

Blackstone.com (Web), Intranet portal,
& Registered Product Websites

Audiences

Institutional Investors, Prospective Investors,
Compliance Officers & Employees

The Problem

The system Blackstone had inherited was not scalable. Outdated, fragmented, reliant on one-off assets that accumulated faster than they could be governed. Evergreen design wasn’t considered from an authorable or platform standpoint — components weren’t built to last beyond the page they shipped on. Patterns repeated across surfaces with no shared source of truth. Internal tools and the public site spoke different visual languages. Every new feature compounded the debt. For a firm whose brand promise is institutional rigor at scale, the digital infrastructure didn’t match.

Scope

Brought in alongside one other designer to build the design system that would unify it. I led on system architecture, competitive analysis, legacy content audit and lift, scalable component design, templates and documentation, UX strategy, UI auditing, and net-new component backlogging. Specialized workstream — partnered with a data visualization engineer on chart systems and financial report templating for investor decks and internal analytics. The artifact you’re viewing documents the foundations and components that came out of that engagement: typography roles and locked tokens, a light/dark theme color system with a dedicated viz palette, UI glyph and editorial icon sets, the chart and map library, the full UI component spec sheet (buttons, dropdowns, tabs, accordions, cards, forms, image blocks, video, tables), and the responsive grid behavior that ties it all together.

Approach

One foundation. Two surface contexts. No parallel systems. Foundations stayed audience-agnostic. Components carried context-appropriate density without forking. A button on Blackstone.com renders for an investor evaluating credibility — the same button on the employee portal renders for an analyst running a workflow at speed. Different stakes, same design language. Authorable from the start. Evergreen by construction. WCAG 2.1, ADA, and SEC accessibility validation ran during the audit, not as a retrofit. Tokens were defined once and inherited everywhere. Hover, focus, disabled, and filled states were specified on every interactive element. Motion was held to two timing curves so transitions felt like one product, not many.

Outcomes

A unified design system serving public investor-facing surfaces and internal employee tooling from one source of truth. Legacy one-offs rationalized or retired. Templates and documentation positioning downstream teams to ship without rebuilding foundations. Data visualization and financial reporting patterns designed for cross-surface reuse. Accessibility embedded at audit, not after launch. The system shipped with a documentation layer dense enough that engineering can implement off the spec without follow-up — the artifact you’re reading is part of that layer.