10 Digital Signage Mistakes Businesses Make (And How to Avoid Them)
Digital signage rarely fails on day one — it fails quietly over six months. These are the ten mistakes that do it, from consumer panels on a commercial duty cycle to screens nobody owns, and what to do about each.
On this page
Digital signage rarely fails on day one. The screen goes up, the content looks good, somebody photographs it for the company chat, and everyone agrees it was worth doing. The failure happens quietly over the following six months, and by the time anyone raises it the screen is either off, showing something from March, or showing something nobody can read from where they actually stand.
The same handful of digital signage mistakes account for most deployments that end up as expensive wall decoration. They are set out below in the order they bite: hardware first, then content and scheduling, then the commercial and organisational failures. Some are solved by better software. Several are not, and this guide says so.
The pattern behind almost every failure
Signage is usually specified as a purchase and needs to be run as a publication. That mismatch causes nearly everything below.
A purchase has a completion date. You buy panels, mounts and a subscription, an installer visits, and the project is signed off. A publication has no completion date — it has an editor, a schedule and a next issue. Every deployment still working two years later has quietly become the second thing.
If you read nothing else: before buying anything, write down who will change the content, how often, and what happens to that responsibility when they leave. A deployment with a named owner and cheap hardware beats one with commercial panels and no owner every time.
Mistake 1: Running consumer televisions on a commercial duty cycle
What it looks like. Nine months in, the panels at the busiest site are visibly dimmer than the identical ones in the back office, one has a ghost of the menu header burned into the top third, and two have failed. The retailer has declined the warranty claim, citing commercial use.
Why it happens. A consumer television and a commercial display of the same size look identical on the shop floor, and the consumer one is a fraction of the price. The difference stays invisible until the panel has been running long daily hours for the better part of a year.
What it costs. The replacement panel, the installer visit, the days the screen was dark before anyone got round to it, and the credibility of whoever argued for the project.
The fix. This is a specification decision and no platform can rescue you from it. Ask for the datasheet and read three lines: rated operating hours per day, brightness in nits, and whether portrait mounting is supported. Consumer sets are specified for domestic evening viewing; commercial displays state a duty cycle and have the heat management to back it up. Brightness matters most in daylight, and a panel that dazzles in a showroom is washed out in a south-facing window.
Consumer televisions are not always wrong — eight hours a day in a shaded corridor is a reasonable place to save money. What is never right is buying the cheap panel without knowing there was a decision to make. Either way, schedule the display to sleep outside trading hours; hours not run are the cheapest life extension there is.
Mistake 2: Picking screen size from a budget rather than a viewing distance
What it looks like. A 43-inch panel at the far end of a canteen. A menu board that reads perfectly from underneath it and not at all from the back of the queue, which is the only place anyone reads it from.
Why it happens. Screen size is the one number in the quote everyone understands, so it becomes the budget lever. Somebody trims two inches off every panel to make the total work, and it looks harmless because nobody wrote down how far away the reader stands.
What it costs. A screen that cannot be read at its viewing distance is not a degraded screen, it is a dark one. It produces nothing while still producing a subscription line and an electricity bill.
The fix. Measure the distance to the furthest person you need to reach before choosing a size, then work backwards from text height using the standard rule of thumb: roughly one inch of capital-letter height per ten feet of viewing distance, or about one centimetre per 1.2 metres.
| Furthest viewer | Minimum text height | Typical setting | What it forces you to cut |
|---|---|---|---|
| 2 m (6 ft) | About 1.7 cm | Counter or till point | Little — close to desktop reading |
| 4 m (13 ft) | About 3.3 cm | Menu board read from a queue | Descriptions; keep item and price |
| 8 m (26 ft) | About 6.7 cm | Concourse, reception, office wall | All but a headline and one line |
| 15 m (50 ft) | About 12.5 cm | Shop window seen from the pavement | All body copy. One message only |
The table runs in both directions, which is the useful part. If your content will not fit at the required height, the options are a bigger panel, a second panel, or less content — and less content is usually correct. The retail zone-by-zone playbook works through this per store area.
Mistake 3: Content that cannot be read from where people stand
What it looks like. Pale grey type on white. A caption laid over the busy part of a photograph. A brand font that is elegant at twelve point in a brochure and mush at four metres.
Why it happens. The content is designed on a laptop at fifty centimetres and signed off by someone looking at a proof on a monitor. Every review in that chain happens at the wrong distance.
What it costs. The same as mistake two, except the fault is entirely fixable and usually goes unfixed for years, because everyone involved has only seen the content where it looks fine.
The fix. Check contrast rather than trusting your eye — the W3C accessibility guidelines publish ratios that are a sensible floor for signage, and content clearing them also works for viewers with low vision, who on a public screen are a material share of your audience. Put text on a solid block rather than over imagery, set a minimum type size per screen from its measured viewing distance, and refuse anything below it.
The test that settles arguments takes two minutes: publish, walk to the furthest point you care about, and read it aloud. If you squint, lean in or step forward, it fails. The restaurant signage guide applies the same discipline to menu typography.
Mistake 4: Treating signage as a television channel
What it looks like. A three-minute brand film on loop in a reception where the average wait is forty seconds. A corporate video with dialogue playing silently in a lobby. A twenty-item playlist in a lift lobby, so any given item reaches roughly one person in twenty.
Why it happens. The screen looks like a television, so people fill it with television. The content already in the marketing library is broadcast content, and reusing it feels like efficiency.
What it costs. Nothing dramatic, which is why it persists. The screen is on, the content is current, the project looks healthy, and almost nobody sees a complete message.
The fix. Start from dwell time, not from the content you have. Estimate honestly how long someone stands in front of each screen, then make the loop short enough that a typical viewer sees all of it and each item short enough to land in a glance. A window passed at walking pace needs one message legible in about three seconds; a two-minute queue can carry a longer rotation. Assume no sound, always: anything depending on audio is content with a missing half.
Where dwell time is short but the screen is large, split-screen layouts are the honest answer — a persistent zone carrying what everyone must see, plus a smaller rotating zone for the rest. Qmanja Signage supports up to twelve zones, though two or three is right for most sites. The features overview covers the layout and scheduling model.
Mistake 5: One playlist, all day, every day
What it looks like. Breakfast items still on the board at four in the afternoon. The staff safety briefing running on the customer-facing screen. A recruitment advert playing to an empty building at eleven at night.
Why it happens. A single playlist is what you build on day one because it is the simplest thing that works, and it does work. Dayparting never becomes urgent, because the screen is never broken — only ever slightly wrong.
What it costs. Relevance, which is the entire mechanism by which signage does anything. A screen showing something inapplicable teaches passers-by that this wall is not worth checking.
The fix. Set day-and-time rules once. The decision is not technical — it is a list of the moments in your week when what the screen should say changes: opening, the breakfast-to-lunch switch, the mid-afternoon lull, the pre-close push, weekends, early-closing days. Most sites turn out to have only a handful of genuine transitions, and each is a rule you write once.
[SCREENSHOT: schedule view showing a weekday daypart rule alongside a different weekend rule for the same screen]
Two questions before you rely on this. What happens when two schedules overlap on one screen — silent last-write-wins is how a Sunday menu ends up running on a Tuesday. And can a rule apply to a group of screens at once, because setting the same rule forty times means getting one of them wrong. The restaurant solution pages cover dayparting in operational detail.
Mistake 6: No plan for what the screen does when the network drops
What it looks like. Saturday morning, the broadband is down, and every screen shows a connection error, a spinner or the media player's home screen. Or — subtler and more common — the screens play on perfectly, nobody notices the site has been offline for eleven days, and last week's promotion is still running.
Why it happens. Nobody asked during procurement. Offline behaviour never appears in a demo, because demos happen on working networks.
What it costs. The first version costs you every screen during exactly the period you least want them dark. The second costs you accuracy with no visible symptom, which is worse — you find out when a customer asks for a price that no longer exists.
The fix. The behaviour worth having is media cached on the device, so the screen keeps playing its last published schedule indefinitely and reconciles itself when the connection returns. That is how Qmanja Signage players behave; what you lose offline should be limited to publishing changes, live streams and live status. Caching then creates silent staleness, so you also need an alert when a screen stops checking in, routed to a person rather than an inbox nobody reads.
Then test it the only way that counts. Pull the network for ten minutes and watch. Pull the mains, wait thirty seconds, restore it, and time how long until content is back without anyone touching a remote. The Android TV setup guide covers the settings that decide whether that recovery happens.
Mistake 7: No proof the screen was ever actually on
What it looks like. Somebody asks whether last month's campaign ran on all eleven screens. The honest answer is that it was scheduled on all eleven, which is a different claim, and nobody can improve on it.
Why it happens. Publishing feels like completion. You publish, the screen in front of you changes, and the screens you cannot see are assumed to match the one you can.
What it costs. You cannot evaluate the deployment, because you cannot separate "the content did not work" from "the content did not play". You cannot invoice for advertising space without a delivery record. And you cannot detect slow failures, like the branch whose panel has been off since April.
The fix. Two mechanisms, and they are not the same. Check-in monitoring tells you the device is alive and reachable. Proof-of-play logging tells you which item appeared on which screen and when, and only that settles the campaign question. Qmanja Signage includes proof-of-play reporting on paid plans; when comparing platforms, check whether it is included or sold as a module, and how long logs are retained.
Neither mechanism can see the panel itself: a player will report that it played a file while the display in front of it is switched off or on the wrong input. Closing that gap needs HDMI-CEC power control where the hardware supports it, and otherwise a human — build a thirty-second look at every screen into somebody's opening routine.
Mistake 8: Buying licences that punish growth
What it looks like. Three screens at a price everyone was happy with, then the second location. The per-screen rate does not move but a tier boundary does, or the features you now need — cross-site scheduling, a role for the new manager, reporting — turn out to sit on a different plan.
Why it happens. Signage is bought for the pilot. The pilot is small, so the cheapest pilot option wins, and the pricing model is never stress-tested against the estate you intend to have in three years.
What it costs. Usually a migration: new software, re-paired devices, rebuilt layouts, retrained staff. Occasionally worse — a deployment frozen at four screens because screen five triggers a step change nobody has budget for.
| Pricing model | How it is presented | Where it hurts as you grow |
|---|---|---|
| Flat per screen, per month | One rate, features included | Predictable — growth costs what you forecast |
| Per screen plus add-ons | A low headline rate | The real rate is unknown until you list every feature you need |
| Tiered plans | Good, better, best | One needed feature moves every screen you own up a tier |
| Minimum commitment | A competitive per-screen price | A 25-screen minimum on an 8-screen estate is a rise in disguise |
| Perpetual per-device licence | Buy once, own it | Every replacement device is a re-purchase unless it transfers |
The fix. Price the estate you expect in three years, not the pilot, and ask for a written quote covering every feature on your requirements list rather than a rate card. Three questions settle most of it: is there a minimum screen count or contract term, does a licence transfer when a player is replaced, and what is the price at double the screens.
For a concrete comparison point: Qmanja Signage is free forever for one screen with 200 MB of storage and no card required, then $6.99 per screen per month, or $4.99 per screen per month billed yearly, with Business pricing quoted at twenty screens and above. The free versus paid comparison covers where a free tier suffices, and the buyer's guide lists the questions worth putting to a vendor in writing.
Mistake 9: Nobody owns the content
What it looks like. The screens work. The scheduling works. The content is from March. Everyone knows it is stale, everyone assumes somebody else is dealing with it, and nobody has it in their objectives.
Why it happens. Signage is installed by whoever championed it — IT, facilities, a marketing manager on a project — and then the project ends. Ongoing content is recurring work that was never resourced, because at sign-off the screens were full and the problem was invisible.
What it costs. Everything, eventually. Stale screens are worse than no screens: they train the audience to ignore that wall, and refreshing the content does not immediately bring people back. This is also the failure no software fixes — better tools lower the effort per update, they do not create the person.
The fix. Name one person per screen group, in writing, with a stated cadence, and put it in their objectives rather than their goodwill. Then shrink the job, because a role needing an hour a week lapses and one needing ten minutes does not.
- Make as much content as possible update itself. A live web source, a dashboard URL or a live stream never goes stale.
- Keep the structure fixed and rotate one small zone, so the weekly job is one item and not one redesign.
- Delegate locally with scoped permissions, so a shop manager can post local content without breaking the head-office template.
- Put a review date in a shared calendar. Almost every stale screen would have been caught by a recurring fifteen-minute diary entry.
Multi-site organisations feel this hardest, because the distance between the person who can publish and the person who notices the problem is greatest. The campus deployment guide covers departmental ownership in detail.
Mistake 10: No plan for the day the person who set it up leaves
What it looks like. The screens have shown the same thing for four months. The person who built it left in spring, the account is registered to their work email, and nobody knows which subscription line on the card statement is the signage one.
Why it happens. Signage is set up by one enthusiastic person, quickly, with whatever account was to hand. It is never handed over because it never breaks — it runs fine right up to the moment somebody needs to change it.
What it costs. Mildly, a support conversation and a week of stale content. Badly, the deployment is orphaned and rebuilt from scratch: new account, every screen re-paired, every layout remade — while the recurring charge carries on, because nobody knows what it is for.
The fix. Treat the signage account like any other business system, which mostly means four unglamorous things.
- Register the account to a role address, not a person — a shared operations or marketing address that outlives any individual. This alone prevents most of the damage.
- Give at least two people administrative access. One is a single point of failure, and the failure is always unplanned.
- Write a one-page runbook and store it with your other operational documentation: which account, where the credentials live, how many screens, where they are mounted, who to contact at the vendor.
- Name screens so a stranger can find them. "Camden — counter, left of till" rather than "Screen 7", with a matching label on the device.
Pairing is what people worry about most in a handover, and it is the easy part: the player displays a six-character code, you enter it in the dashboard, and the screen claims itself within seconds — no password on the device, no configuration to transfer.
[SCREENSHOT: pairing screen showing the six-character code]
Because pairing is that light, a failed player is a swap rather than a project, and one pre-configured spare per site is cheap insurance. The players and devices page lists what runs today: any modern web browser, Android TV, Amazon Fire TV and Windows, with macOS, Samsung Tizen and LG webOS in development and iOS in review.
A thirty-minute audit of a deployment you already have
Most people reading this already have screens up. This is the fastest way to find out which of the ten you are living with — do it in the building, not from a desk.
- Stand at the furthest point a real viewer stands and read every screen aloud. Anything you squint at fails mistakes two and three.
- Time one full loop against how long people actually stand there. Loop longer than dwell is mistake four.
- Check what is on screen against what should be on screen at this hour. A mismatch is mistake five.
- Unplug the network at one screen for ten minutes. Whatever happens next is your offline plan, whether you chose it or not.
- Ask who changed the content last, and when. If nobody can answer immediately, that is mistake nine, and probably ten.
- Open the invoice and price your intended screen count in three years. That is mistake eight, quantified.
The two that fail most often are the reading-aloud test and the question about who changed the content last.
Where to start
The pattern in all ten is the same. Signage fails when it is treated as something you install rather than something you run. Hardware chosen for a duty cycle it will never see, content designed at reading distance for an audience four metres away, playlists that never change because nobody owns them — none of these are difficult problems. They are problems nobody was assigned.
So start at the cheap end. Name the owner. Measure the distance. Write down the moments in the week when the message should change. Then prove your offline behaviour by unplugging something. That is a morning's work, and it prevents most of what is on this page whatever platform you use.
Test the fixes on one real screen. Qmanja Signage is free forever for your first screen — 200 MB of storage, no card required. Pair a spare TV with a six-character code, build the dayparting rules you just wrote down, then pull the power and watch it come back on its own. If you would rather see it against your own sites and screen count first, book a demo or get in touch.
