Bloomberg · Design Challenge
An intelligent alert system for traders - designed solo in 4 days
Quick Brief - for the hiring manager
Problem
Traders tracking thousands of securities miss critical price events. Design a complete Alert system for Bloomberg Terminal - field-value and field-field comparisons - from scratch in 4 days.
My Role
Solo interaction designer. Owned every phase end-to-end: scoping, competitive research, personas, user flows, wireframes, alpha testing, and V2 iteration.
Impact
5 production-quality alert screens delivered in 4 days. Alpha testing with real traders surfaced 4 key improvements incorporated into V2.
Approach
Scoped the alert workflow into 5 screens. Analyzed 10 trading platforms. Designed for 2 trader archetypes. Integrated keyboard shortcut (Ctrl+Shift+A) into Terminal conventions.
Outcomes
V2 incorporated alpha feedback: "Dismiss All," alert cloning via shortcuts, watchlist-based alert creation. Full interactive prototype and interaction spec delivered in 4 days.
Learnings
Designing for an unfamiliar platform under pressure means prioritizing conventions over creativity. Mathematical complexity in alert logic demands early alignment with data teams before committing to interaction models.
Duration
4 days
Screens Designed
5 complete screens
Versions
V1 + Alpha-tested V2
Who
Solving a design challenge from Bloomberg for an Experienced Interaction Designer role.
What
Creating an Alert System for Bloomberg Terminal.
Why
To alert users to securities when specific data events occur.
How
By letting users combine arithmetical and logical parameters in flexible configurations for alert notifications.
The Challenge
Four days. A blank terminal screen. A brief demanding an alert system with nested logical operators for traders who live and die by price movements. The constraint wasn't just time; it was designing for a platform, audience, and interaction paradigm I had to absorb before I could create for it.
Bloomberg Terminal is keyboard-first, information-dense, used by professionals with years of muscle memory around its conventions. Any design that ignored this would fail before it shipped.
Two Alert Types
Field-Value: "Apple Last Price exceeds $600"
Field-Field: "S&P 500 Last Price falls below S&P 500 52-week Low"
Field-Field: "S&P 500 Last Price falls below S&P 500 52-week Low"
Design Process
Research & Insights
Day Traders vs Passive Traders
Two distinct user types with different alert behaviors. Day traders need instant, granular alerts; passive traders need broader, less frequent signals. The UI had to serve both without added complexity.
Keyboard-first is non-negotiable
Terminal users have years of keyboard muscle memory. Mouse-heavy alert creation would be a dealbreaker. Ctrl+Shift+A became the primary entry point.
5 screens for the complete workflow
Alert Sources (create CTA), Setup, Notifications, Alert Display (popup), and Edit/Delete. Every path through the alert lifecycle needed explicit design.
Key Design Decisions
01
Keyboard shortcuts as primary UX
Ctrl+Shift+A to create an alert anywhere. Duplicate with a single keystroke. Dismiss All with one action. Every interaction matched the muscle memory of experienced Terminal users rather than fighting it.
02
Grouping notifications by security
Alpha testing revealed frustration with scattered notifications. V2 grouped alerts by security (all AAPL together, all IBM together), dramatically reducing cognitive overhead during high-volume sessions.
03
Clear All vs Dismiss All as distinct actions
A critical distinction surfaced in testing. "Dismiss" removes from view; "Clear" deletes permanently. Traders needed both: temporarily clearing noise without losing alert history.
Outcomes & Impact
4 Days
End-to-end interaction design: scoped, researched, designed, tested, iterated
5 Screens
Full alert lifecycle: Create → Setup → Notify → Display → Edit/Delete
V1 → V2
Iterated based on real alpha testing with Bloomberg Terminal users
10 Platforms
Competitive analysis: Robinhood, TradingView, Zerodha, E-Trade, and 6 others
Learnings
Constraints breed clarity. Four days forced ruthless prioritization: what must work perfectly vs. what can be deferred. That discipline produced a cleaner design than an open-ended brief would have.
Platform fluency is a design skill. Understanding Terminal conventions, mental models, and muscle memory was as important as any visual or interaction decision.
Mathematical complexity demands early alignment. Nested logical operators in alert conditions required data model clarity that should have involved a data analyst from day one.