An empty screen should say which empty
Nothing to order, or nothing loaded? A purchasing screen that goes blank can mean either, and a manager cannot tell them apart. The fix is words, not spinners.
Open your ordering screen on a Tuesday morning and see a blank panel. What just happened?
It could be the best possible news: everything is above its par level and you have nothing to buy. It could be that this venue has no suppliers set up yet. It could be that the screen asked the server a question and got an error back. From where you are standing, all three look identical, and only one of them means you can go and do something else.
The three empties are different jobs
Nothing to do is a result. It deserves a sentence that says so with a little detail — "Nothing is below par at this site. Everything counted is at or above the level you set for it. You can still build an order by hand." That last clause matters, because the manager standing there may know something the stock count does not.
Nothing set up is a task. It should name the next step, not describe the hole: "No suppliers with products yet." tells you where to go. A spinner that never stops tells you nothing.
Nothing loaded is a fault, and it is the only one of the three that should look alarming. A screen that fails quietly trains people to wait, refresh, wait again, and eventually decide the software is slow. A screen that says it could not fetch something sends somebody to fix it.
Why this is not a design nicety
We had two purchasing screens fail for a day this week. What made it a day rather than an hour is that a dead screen and an empty one looked the same from outside. Anyone who opened it that morning had a perfectly reasonable explanation available — we must be well stocked — and no reason to report anything.
That is the real cost of an ambiguous empty state. It does not just confuse; it supplies an innocent explanation for a fault, and the fault then survives until somebody happens to look from the other side.
A test you can run on any system you use
Pick the three screens your team looks at most. For each, work out what it does when there is genuinely nothing to show, and whether that is distinguishable from a failure. If they are not distinguishable, you have a blind spot that no amount of monitoring will cover, because the monitoring only knows about the errors the software chose to report.
Then look at whether the empty state names the next action. "No results" is a dead end. "Nothing is below par — you can still build an order by hand" is a door.
The same rule at the counter
This applies away from screens too. A kitchen that hears nothing from the pass cannot tell "no orders" from "the printer stopped". A supplier who does not confirm cannot be told from one who never received the email. In every case the cure is the same and it is unglamorous: say which kind of nothing this is.