BLACKSTONE

ROLE
UX Design Consultant

CLIENT
Blackstone
New York, NY

TIMELINE
September 2022 – March 2023

TEAM
Two UI/UX Designers + One
Data Visualization Engineer

SURFACES
Blackstone.com (Web) + Intranet portal

AUDIENCES
Institutional Investors, Prospective Investors,
Compliance Officers & Employees

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 PROBLEM
The system Blackstone had inherited was not scalable. It was outdated, fragmented, and reliant on one-off assets that had accumulated faster than they could be governed. Critically, evergreen design was not 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.

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.

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.