Technology
The case for slower dashboards
A field note from two weeks spent removing urgency from a status page that had learned to panic.
I spent the first half of February rewriting the incident board for a lab in Olympia that measures river sensors. The old screen refreshed every three seconds, blinked red when a battery dipped below fourteen percent, and trained perfectly reasonable people to stare at it like a campfire with quarterly goals.
The graph was correct, and still lying
The problem was not accuracy. Every number matched the device logs, but the interface collapsed weather, hardware age, and technician travel time into one bright sense of catastrophe. We changed the cadence to ten minutes, drew the trend line in blue, and made the alarming parts explain themselves before asking anyone to move.
Fast data is not the same as useful data; it is just data with its elbows out.
By Friday the room was quieter. Nobody celebrated, which is usually how infrastructure admits it has improved. The dashboard now waits long enough to be read, which turns out to be the smallest possible act of respect for a person trying to do math while wearing rain boots.