Field note · · 4 min read
Planning content before selecting display hardware.
A display is a platform for an ongoing experience. If content is left until after procurement, the team inherits decisions about shape, resolution and operation that may have little connection to what the display needs to do.
Define the job in the space
Begin with the audience and the purpose. Is the installation helping people find their way, understand a product, wait comfortably, participate in an interaction or experience an artwork? These uses lead to different content rhythms, information densities and system requirements.
A useful brief describes where people encounter the display, how much time they have and what they should understand or do. A person walking through a concourse cannot be expected to follow the same sequence as a seated visitor. Architectural media can also work through texture, light and movement without carrying a conventional message. That is a valid creative intention when it is defined deliberately.
Develop a small but representative content set
Before selecting hardware, create examples of the material the system will actually carry. Include a typical piece, a demanding piece and an everyday fallback. For information-led signage, test the longest realistic wording and the smallest essential text. For architectural media, test the intended composition and motion across the whole surface.
Use these samples to establish duration, hierarchy, contrast and safe areas. Consider language variants, captions and whether the experience can be understood without sound. Review flashing and motion with accessibility in mind. For wayfinding or essential information, confirm the requirements for the environment and provide a dependable alternative when digital content is unavailable.
These samples are working tools, not a completed launch campaign. Their purpose is to reveal requirements while geometry, viewing positions and technology can still change.
Let content shape the canvas and system
A panoramic composition may need an unusual native resolution. Separate surfaces may require synchronized playback. Real-time content may need a rendering engine, data access and defined latency. Interaction may require sensing, feedback and a clear idle state. A simple scheduled video loop has a different technical burden.
Record the physical dimensions, pixel map, frame rate, file formats, colour workflow and output topology in a shared content specification. Confirm how scaling, cropping and mapping will be handled. Test the proposed media on the actual class of playback hardware; a file running smoothly on an editing workstation does not establish that it will play reliably on the installed system.
Coordinate this work with architecture and integration. Display placement, lighting, power, ventilation, cable paths and service access affect what can be delivered. Content planning should inform those decisions early, while technical constraints feed back into the creative direction.
Design publishing as an everyday workflow
Name the people who will create, approve, publish and maintain the content. Decide how updates move from a draft to a review environment and then to live displays. Establish permissions, scheduling rules, version history and a way to roll back an incorrect release.
For a multi-site network, define which material is central and which can be changed locally. Resolve time zones, opening hours, campaign expiry and exceptions before launch. Preview each template in its intended layout so that an unexpected headline or image does not break the composition.
Live data needs an owner too. Specify the permitted source, update interval, credentials, freshness threshold and behaviour when data is stale. Do not leave an expired value on screen indefinitely simply because the player is still running.
Plan the quiet days and the failure states
The launch is one moment in a longer operating life. Budget for routine updates, seasonal changes, template maintenance and content review. Establish who checks that the experience remains useful after the initial project team has moved on.
Define what happens when there is no current campaign, a network link drops or a data service fails. Locally stored fallback media can keep an appropriate experience on screen where the selected platform supports it. Test that behaviour, including restarts and recovery. Also confirm what monitoring can actually observe: player connectivity, application health and visible output are different things.
Keep source files, licensed assets, fonts, export settings and system documentation in a controlled handover. Confirm rights for the intended display use, territory and duration. Assign responsibility for renewals and for retiring content that is no longer licensed or relevant.
Commission the experience, not only the equipment
Acceptance should include representative content, schedules, synchronization, data states, operator tasks and recovery procedures. Walk the audience route and review the installation under the lighting conditions that matter. Confirm that the operating team can publish an update and restore the agreed fallback.
Agree how success will be assessed against the original purpose. That might involve checking comprehension, observing interaction completion or reviewing content freshness and availability. A screen being switched on is a technical milestone; a useful, maintainable experience is the outcome. Planning content early gives the hardware decision a clear job to serve.