Bloomberg · Case study
DATA<GO> Navigation
Bloomberg’s data marketplace was organized the way Bloomberg is organized. I rebuilt its navigation around what clients need, without breaking the business lines that sales and pricing run on.
- Role
- Interaction Designer, lead on DATA<GO>
- Team
- PM, engineering, 5 sales reps, 1 visual designer
- Timeline
- 10 months, launched March 2026
- Platform
- Web, about 9,750 monthly users
The UI here is recreated from memory, not taken from the product. Some details are changed or left out for confidentiality.
The problem
A store organized by org chart
DATA<GO> is where clients and Bloomberg’s sales team browse and buy Enterprise Data, a business projected at over $300M in 2026. Data License sales had flattened even as the catalog grew, and sales and product asked design to promote new products. A client had told me months earlier that browsing was confusing, so I suspected something deeper.
Everything was filed under business lines: Per Security, Bulk, Real-Time, Indices. They describe how Bloomberg packages and prices data, not what a client is looking for. Bulk was where it hurt most. Bloomberg wants to sell curated Bulk packages, but clients couldn’t tell what was inside one, or whether it fit their business. Clients who couldn’t find something called sales. Clients who didn’t know it existed never asked.
Confidential
The rest is password protected
This case study shows internal Bloomberg work. If I shared a password with you, enter it below. If not, just ask and I'll send it.
That password didn't work. Try again?
Email me for the passwordEnd of case studyBack to top ↑
