← Back to work

Bloomberg · Terminal

Redesigning Speed Dial.

In 2013, Bloomberg was rethinking the terminal experience to make it simpler and more relevant to the people who lived inside it all day. As an intern (and then co-op) on that effort, I helped redesign Speed Dial — the application traders and brokers used to manage contacts and pricing distribution.

Role
UX Design Intern · led research and design across both phases
Product
Bloomberg Terminal · Speed Dial
Timeline
May 2013 — Dec 2013
Platform
Bloomberg terminal · Custom hardware & keyboard
Bloomberg Speed Dial redesign hero

My role

Research, design, and iteration end-to-end.

I was responsible for conducting the initial research, translating the findings into design directions, and iterating on those designs through rounds of user testing.

Domain knowledge

Learning the terminal before touching the design.

To genuinely understand our users' problems, we had to get familiar with the Bloomberg terminal — both the unique hardware and the software experience. Spending time inside it ourselves grounded everything that came after.

Bloomberg terminal hardware and interface
The Bloomberg terminal — image courtesy of Bloomberg.

Challenge

A legacy tool sitting on a critical workflow.

Speed Dial was how traders and brokers maintained contacts, set aliases, shared their network with teammates, and pushed pricing information out to the people who needed it. Because so much real communication happened through it, every usability issue carried weight. The redesign needed to untangle a legacy app without disrupting the daily work flowing through it.

Speed Dial workflow diagram
The communication workflow Speed Dial sat on top of.

"Phase I asked what the ideal product looks like. Phase II asked what we can ship."

— How the project was structured

Project structure

Two phases — exploration, then constraints.

The work split cleanly into two phases. Phase I focused on user needs and design exploration. Phase II layered in stakeholder requirements, engineering constraints, and the broader terminal vision.

Two-phase project diagram
The two-phase structure.

Phase I · Research

29 users, three weeks, semi-structured interviews.

We ran semi-structured interviews with 29 users across different roles over three weeks — deliberately mixing job functions to surface how usage patterns varied across the desk.

User interview setting
A typical interview session.

Phase I · Literature review

Mapping the territory before sketching.

In parallel with the interviews, the team ran a competitive analysis and reviewed research literature to build a foundational understanding of the problem space.

Stack of research papers
Research and competitive review.

Phase I · Data analysis

Open coding and affinity mapping.

We analyzed the interview data quote by quote using open coding and affinity mapping — letting themes emerge from the transcripts rather than projecting them onto the data.

Affinity map of interview themes
The affinity map that came out of the interviews.

Phase I · Idea generation & design

Many concepts, refined down to three.

From the findings I generated a wide set of design concepts, then refined them with feedback from domain experts. That process narrowed the field down to three primary directions worth testing.

Sketches of design concepts
Early sketches and concept exploration.

Phase I · Testing

Three concepts, paper-prototyped with the original users.

We tested all three concepts as paper prototypes with the same users we had originally interviewed — so the feedback could connect back to the problems they had described in their own words.

Three concept visualizations
The three tested concepts.

Phase I · Final design

One unified design, drawing on all three.

The testing results informed a single unified design that combined the strengths of each of the three concepts.

Phase I final wireframe
Phase I final wireframe.

Phase II · Reviewing the proposed design

Where the design met engineering reality.

Meetings with product management and the development team surfaced technical constraints that meant parts of the proposed design needed to be reworked.

Layout exploration sketches
Layout exploration after the engineering review.

Phase II · Iterating

Refining the left and right panels.

We went through several rounds of refinement focused on the left and right panels — tightening the interaction model until each panel earned its place.

Left panel wireframes
Left panel iterations.
Right panel wireframes
Right panel iterations.

Phase II · Final design

Group and Individual views, with specs.

We converged on final wireframes that covered both the Group and Individual views, then handed off detailed specifications to development.

Final wireframes for Group and Individual views
Final wireframes — Group and Individual views.
Specification samples
A sample from the specification handoff.

Overall impact

From a 3-month internship to an 8-month co-op.

The work was well received, and the engagement was extended from a 3-month internship into an 8-month co-op so I could keep contributing to the broader terminal redesign.

  1. Unified design

    One pattern, broad reach.

    The testing results converged on a single unified design used across the affected terminal workflows, replacing fragmented one-off treatments.

  2. Engagement extended

    3-month internship → 8-month co-op.

    Strong reception of the work led the team to extend the engagement so I could continue contributing to the broader terminal redesign.

Reflections & design takeaways

Designing for the Bloomberg Terminal taught me that on a screen this dense, restraint is the design move. The win wasn't in inventing a new pattern — it was in finding the one pattern that could carry across the affected workflows without disturbing the muscle memory traders had already built up over decades.

Get in touch

Have a complicated problem?
I'd love to hear about it.