The buyer of an automation system evaluates it in a demo. The operator lives inside it, the dispatcher, the reviewer, the coordinator who works in the queue every day, catches its mistakes, and decides quietly whether the system gets adopted or worked around.
We design for the operator first. In practice that means the daily surfaces get the design attention that usually goes to dashboards: the queue, the approve/reject controls, the exception view, the undo button. The executive summary can be plain. The screen someone stares at for six hours cannot.
The second-order effects
Operator-first design keeps surprising us in good ways. Systems get adopted faster, because the person with the most power to reject them was the first to be convinced. Feedback gets sharper, because operators report problems in terms of the work, not the software. And the systems last longer, an operator who trusts a system defends it through reorganisations, budget reviews, and changes of management.
“Buyers approve systems. Operators keep them alive.