Bloomberg · Case study

Notification Hub

One place for clients to see the changes coming to their data, and what to do about them, replacing weekly emails and phone calls.

Role: Interaction Designer & researcher
Team: 1 PM, 1 designer, 3 engineers
Timeline: 9 months, launched Q2 2024
Platform: Web, Customer Service Center

The UI here is recreated from memory, not taken from the product. Some details are changed or left out for confidentiality.

100clients across 8 major firms at launch, using it from day one

85%of visits open a notice’s details, across about 25 unique visits a day

“This is a no-brainer, incredible improvement. I can tell you with certainty that [firm] has saved time and money.”

Client, after launch

The problem

When the data changes, client systems break

Enterprise Data clients don’t use Bloomberg’s data in the Terminal: they buy it and host it in their own systems. So when a source changes, through a merger, a new regulation or a new exchange, their code can break: lost data, broken pipelines, and money down the drain.

Bloomberg’s Notifications team warned them with a weekly email and a spreadsheet attachment. It was hard to parse, full of changes they didn’t care about, and vague about what to do. Many issues went unresolved, and clients leaned on Bloomberg’s teams to fix them.

Original