The alert nobody unmutes

The Friday of a holiday week is the loudest day of the year for a reporting tool.

Every alert in every account is built against a comparison with a normal week. Sales down sixty per cent on the trailing average. Cost per order up. Conversion rate collapsed. Budget underspending. Traffic anomaly detected. The account is not broken. The country is at a family lunch.

Nobody sat down and decided to have nine alerts. Each one was free to switch on, and free is how there came to be nine. A threshold costs nothing in the moment it is created and takes its payment later, out of somebody's attention, in a week nobody was thinking about when they made it.

The payment gets collected like this. The person responsible is on a road between two family houses. The phone goes off for the fourth time in an hour with something that is not true. They mute the channel, which is the correct decision that day and the only one available to them.

Then the mute stays on. It will still be on in September, when a real alert fires into a silenced channel and a genuine break runs for eleven days before anybody notices it.

An alerting system that has not been told about the calendar teaches a team, once and permanently, to ignore it. No threshold is clever enough to undo that afterwards. What the tool needs is the holiday calendar, which is the one input nobody in the region thinks of as a setting.