Consumer interfaces are designed for a two-minute visit. Operational interfaces are designed for a twelve-hour stare, and almost every consumer instinct is wrong in that context.
Atlas Fleet's controllers sit in front of the same screen from six in the evening until six in the morning. Everything I would normally do to make an interface feel alive turned out to make their night worse.
Motion means something happened
In a twelve-hour interface, any movement is a claim on attention. If a card animates because it is pretty, the controller learns to ignore movement, and then misses the animation that mattered.
The rule we settled on: motion is reserved for genuine state change. Nothing eases, fades or slides for decoration. It is a severe constraint and it made the product dramatically better.
If everything moves, nothing is worth looking at.
Alerts are a tax on attention
The original system fired a notification per event. Controllers muted it within a week, which is the most honest usability finding you can get.
We replaced notifications with a ranked queue: every event has an owner, a severity and a position. Nothing demands attention; everything is findable in priority order. Mean time to acknowledge fell from eleven minutes to under three.
Trust the expert
These controllers are extremely good at their job. The interface's role is not to guide them, simplify for them or protect them from complexity. It is to show them the truth quickly and then get out of the way.
Working on something where this applies? I take on three or four substantial engagements a year. Start a conversation. It costs nothing and usually clarifies more than it takes.
