The data wall on the visitor corridor is often the company’s evidence that it “already went digital.” Bars rise and fall, flight lines cross a China map, numbers tick in fake-random rhythm. After the tour, supervisors still go back to the office for today’s backlog, and the boss still asks an assistant for the weekly report. The signal that screen sends is not capability. It is: our bar for reviewing numbers can be as low as “looks good.”
The gap versus doing nothing is a more dangerous layer: you chose to display it. A blank wall at least tells people you still run on sheets. A screen that will not click lets the inside give up serious reconciliation—the wall set cannot be asked anyway. Visiting customers and suppliers will treat that screen as a proxy for management: if you cannot ask into your own backlog, is a delivery promise still credible? Same diagnosis as buying BI as decoration; see Buying BI as decoration is the same as doing nothing. What should actually go on the wall is today’s output, backlog, and exceptions—not a strategy map. See What a plant and warehouse screen should show and How a shop-floor screen keeps crews out of the office.
The fix is not a flashier visualization library. Delete KPIs nobody can own. Leave three to five tiles that drill. Refresh by shift, not by animation. Flight lines and a 3D globe almost never enter a decision. Leave budget for API stability and permissions. If it will not open, do not put it on the wall; see If a number cannot open a document, what is the dashboard for. Exhibit versus decision entry: Treating systems as a warehouse exhibit vs a decision entry. Empty frames nobody opens: cut first, then embed in the meeting; see Nobody looks at the dashboard. Is it still worth building.
Accept the visitor screen and the crew screen separately
If you must have an image screen for visitors, write that it is not in the review and does not replace the weekly report. Accept the crew screen at the station: in ten seconds you can see where it is stuck and who should act. Merge both into one “command center” and both sides feel fake. Do not put “big-data driven” on the wall copy. Write cutoff time and one definition sentence. Fake-advanced looks more like a template than honest T+1. If leadership only opens that screen on visitor day, do not count it as a data-project result. Results are how many parallel sheets the weekly meeting stopped, and whether exceptions sit overnight less often. When DaXi delivers a floor wall, a clickable exception list goes into acceptance—not only a design file. To turn a decorative screen into a usable wall, tell the Data service page what is on the wall now. Whether real-time is necessary: Does it have to be real-time, or is T+1 enough.
A fake-busy screen also eats budget and wall space. TV, mount, construction, yearly maintenance—then it only serves ten minutes on visitor day, and the floor still walks to the office for backlog. Put that money into APIs and reconciliation. That is closer to a data capability than buying a larger screen.
Flight lines and a globe almost never enter a decision
Flight lines and a 3D globe almost never enter a decision. Leave budget for API stability and permissions, not particle effects. Effects also glare in a dim plant; crews turn the TV off.
Do not put “big-data driven” on the wall copy. Write cutoff time and one definition sentence. Fake-advanced looks more like a template than honest T+1.
If leadership only opens that screen on visitor day, do not count it as a data-project result. Results are how many parallel sheets the weekly meeting stopped, and whether exceptions sit overnight less often. Separate power, accounts, and refresh for the visitor screen and the crew screen, so you do not swap live data for a demo animation before a visit.