Product (Terminal) Settings
Overview
Bloomberg Terminal
The Terminal Product is very powerful, yet it is not the most intuitive tool to use. Why? Well, as the product grew over the years , hundreds of teams surged and delivered solutions without a design (or engineering) system in place. That led to many inconsistencies across applications, one of them being “app” settings.
There are over 10k apps in the Terminal, and most of them do not use the design system, correct APIs, or guidelines for displaying their settings, making it difficult for the user to find, use and save them intuitively.
Discovery & Research
1 . Current State Sweep
I looked an captured the implemented settings across the top applications on the Terminal. I focused on these 4 attributes:
settings entry point location
overall settings organization & distribution
settings logic (enabling & disabling based on selection)
semantic language
2 . Client Tickets Data
Time the “Help Desk” department spends in client tickets related to settings.
Question types that clients asked about settings (“where do I change…”, “how do I set a default…”, “is there a setting for…”)
Financial and product quality impact that this project would have by reducing overall client complaints, time and resources.
3 . Value Proposition Pitch
I created a presentation for stakeholders showing my analysis on the current situation and the impact that this project could have in clients, Help Desk department, Application Teams (designers and engineers), and overall Terminal modernization.
Low fidelity concept Prototype
Settings design system
