Alerts
After the board pack, the quiet cost of vanity alerts
Board packs create alerts the way leftover rice creates fried rice: something must be done with the extra. A director asks “can we know if this dips?” and a well-meaning analyst wires a threshold at 02:00. Six months later nobody remembers who owns the ping, but it still wakes a CS lead during Songkran.
Vanity alerts are not evil. They are unsigned. An alert without an owner, an on-call window, and a first action is a request for attention with no recipient. B2B Dashboard App Analytics treats that as a contract failure, not a tuning failure. Raising the threshold on an unsigned alert just makes a quieter orphan.
In Alert Hygiene for Product Analytics we print every firing alert from the last 30 days and ask three questions: who is allowed to be interrupted, during which hours, and what is the first human action. If any answer is missing, the alert is switched off in class. Teams are often startled by the silence. Silence is information. It means the grid stopped crying wolf.
A payments reseller cut twenty-two pings to seven. Two of the seven still fire too often at month-end because settlement files arrive late; that is now a documented exception, not a surprise. Arthit in Chiang Mai wrote that the on-call sentence — one line above the threshold — was the only artefact his team still uses weekly.
Do not celebrate a dashboard that is “fully alerting.” Celebrate a list short enough to read on a phone while crossing Sukhumvit. If the list is longer than a board-pack appendix, you are not monitoring. You are decorating the night.