Designing for the control room wall
A dashboard read at two metres for eight hours is a different design problem from one read at fifty centimetres for ninety seconds.
Civiq.plus design · Interface design
Most analytics interfaces are designed for a person leaning towards a laptop, deciding something, and leaving. A civic control room is the opposite: the same screen, in peripheral vision, for an entire shift, with the important event happening perhaps twice.
Almost every convention from the first context is wrong in the second.
Motion is a signal, so it cannot be decoration
In a dashboard read for ninety seconds, an animated counter is a small delight. On a wall for eight hours, it is a false alarm every time it moves. We restrict motion to things that genuinely changed, and even then bias towards a state change that persists rather than an animation that plays.
The corollary is that when something does move, it should be worth turning your head for. Alert surfacing within ten to thirty seconds of a normalized event only helps if the thing that appears is calibrated.
Colour has to survive the room
Control rooms are dim, projectors are inconsistent, and the palette is on a wall behind reflective glass. Semantic colour needs to be distinguishable at low contrast and not rely on saturation differences that a projector will flatten. Every status is carried by shape or label as well as hue, which is also the accessible answer.
Everything must be drillable
A wallboard indicator that cannot be interrogated becomes wallpaper within a week. Every KPI drills to its source evidence and its timeline, and the drill target is the same view an analyst uses at a desk — not a stripped-down popup.
The practical test we use: if someone points at the wall and asks why, can a person at a desk answer within thirty seconds without leaving the product? If not, the indicator is decoration.
