10 digital signage
use cases by sector

What ends up on a staff-facing screen is remarkably consistent across sectors that otherwise have nothing in common:

• Whatever gets explained to every new person. Opening procedure, closing checklist, where things live. In a business with turnover this is repeated dozens of times a year by whoever happens to be there.
• Whatever has a date attached. Deliveries expected, maintenance due, certificates expiring, the shift pattern for next week. All of it currently lives in a group chat, where it scrolls away.
• Whatever gets asked at the counter and answered wrong. Today's substitutions, what is out of stock, which promotion actually applies. Every wrong answer costs a sale and an apology.

The reason this one pays quickly is that the saving is in labour, not in sales, and labour is easier to count. Ten repeated explanations a day at thirty seconds each is an hour, every day, of someone who was hired to do something else. That number is verifiable in a week and does not depend on anybody's estimate of footfall.

It also has a property none of the customer-facing cases have: it does not need to look good. No design, no photography, no brand consistency — a list in large type on a cheap screen in the back room does the entire job. That removes the two things that usually stall a project, which are agreeing on the design and finding the pictures.

There is one condition, and it is worth being honest about it: it only works where people pass the same spot every shift. A kitchen pass, a staff entrance, the back of the counter. In a business where the team is spread out, this belongs on their phones and a screen adds nothing.

If you are choosing where to start, start here rather than with the window. It is cheaper, the benefit is countable within two weeks, and it teaches the habit of updating — which is the thing that decides whether the customer-facing screen ever works.

There are three sources, and they behave nothing alike. A number that is already published somewhere — a booking system, a till, a timetable, a weather feed — costs setup once and then survives neglect. A number that changes rarely and is typed on purpose — prices, opening hours, next week's rota — also works, because the typing coincides with the decision: somebody changed the price, and putting it on the wall is the same act. A number that changes daily with no system behind it — the queue right now, live stock — is where these projects die — not while it is new, but the first week that person is off sick.

Which makes it a filter to run before any sector example. Take each use case you liked and decide which kind it is. If it is the third kind, either find the system that already knows the number or reduce the promise: « fresh bread from 8 » instead of a live counter, « closed on the 15th » instead of a rolling availability board. Dull and still true beats impressive and last updated in February. And two use cases still running after a year are worth more than six launched on the same afternoon.

Notice where the person who runs the place actually stands. They come in through the back, cross the stockroom, spend the day behind the counter and leave the same way. The front door — the one everybody else uses — is the one wall they see least, and often only from the inside, backwards. Which is why the staff board tends to be current and the window has last season on it, in businesses where both exist.

The fix is not discipline, it is placing the check somewhere the routine already goes. Two things work: look at the front screen from the pavement, from outside, once a week — it takes twenty seconds and it is a different experience from seeing it over your shoulder — or give that screen to whoever does arrive through the front, which in most businesses is the newest member of staff and the customers.

And it is worth using the bias rather than fighting it: if there is a use case you know you will not keep up, put it where you cannot avoid seeing it, and put the automatic content — the timetable, the weather, the queue — where you do not pass. It is the same reasoning as sorting by where the number comes from, applied to the human part: anything that depends on a person should be in that person's way.