Pattern library
Bloomberg Terminal's alert model: why silence builds trust, and how to borrow it
A Bloomberg Terminal user names what they care about and the threshold that matters. The terminal stays quiet until something crosses it. Because it is quiet, an alert is read at once, and silence is trusted.
Why it works
- The person names the things they watch (a watchlist), so every alert is about something they chose.
- The person sets the threshold, so an alert is their rule firing, not the product's guess.
- Silence is the default, which makes each alert worth reading at once.
- Speed and precision: the alert names the instrument and the move, and arrives in seconds.
When it holds
- There is a stream of events too large to read, and a few of them matter a lot.
- People can say in advance what matters to them.
Where it breaks
- People cannot name a threshold, so they set none or set everything.
- The product sends alerts to drive engagement; one irrelevant alert and silence stops meaning anything.
- The events are slow, so speed adds nothing and the alert becomes a digest.
Where else it works
- Google Alerts
- You name a query; it sends only new results that match.
- Price trackers for flights and shopping
- You set the route or product and the price; it tells you when it drops.
- Infrastructure monitoring
- Teams set thresholds on their own metrics and are paged only when one is crossed.
Where you could try it
- A B2B SaaS dashboard people check out of anxiety
- A news or research product
- A marketplace with changing prices