16 November 2026

How to test an exhibition stand's multimedia journey before production

Before filming, animation and development, walk through the experience from a visitor's first glance to completion and reset. Check visitor flow, the prototype, the technical brief and the conditions for acceptance.

Illustration of an exhibition stand with a curved screen ribbon, video walls and demonstration areas.

Describe the visitor's action and its outcome

“We need an interactive screen” does not yet describe how the stand will work. Start with a short journey: a visitor notices an invitation, understands the action, makes a choice and receives a response. A catalogue provides product information; a demonstration changes a model or image; a game produces a clear round result.

Record what appears before the first touch and what happens at completion. Where does a conversation with a representative begin? What does the next visitor see? Mark any transition that currently needs a spoken explanation. Use the multimedia project briefing checklist to gather initial questions, then test the specific journey.

Walk the route with the stand team

Place the journey on the exhibition plan. Where is the invitation visible? Where does the participant stand, who watches, and where can a representative join them? Check whether people waiting obstruct the screen or aisle. A shared display and a personal controller may have different roles: one shows the action to bystanders, while the other receives the participant's input.

Rehearse with the people who will run the stand. One plays a new visitor, another a busy representative and another a waiting participant. This can reveal a problem before the application is finished. Plan equipment positions and multimedia actions together; our article on the immersive exhibition stand explores those connections.

Test waiting, cancellation and reset

Describe what happens when an interaction does not end as expected. A visitor may leave, press several buttons or change their mind. An external service may respond slowly, or the network may become unavailable. For each important state, define what appears and what the participant or operator can do.

A server-generated result, for example, needs a waiting state. Decide whether retry and cancellation are available, how a delay differs from an error, and how the next session starts. Set idle timeouts around the actual task so they do not interrupt reading. Offline operation needs its own definition: which functions remain available, and which local data they require.

Prototype the highest-risk part

The first test does not need every finished asset. Choose the dependency that could determine the design: a tablet controlling a screen, selection on a physical model, action recognition or delivery of a result. The prototype should exercise that part with content representative of the intended size and structure.

Record the test conditions: device, orientation, resolution, input method and network. A laptop mock-up helps discuss screen order but cannot establish touch usability on the installed panel. Note where someone misses the next step, waits without an explanation or needs help. After a change, repeat the same route, including cancellation and reset.

Turn decisions into a technical brief

Collect the agreed states, transitions and limitations in one brief. Each action needs defined input, a visible response and a completion condition. Specify devices, content formats, languages, external connections and the process for updating materials. Resolve open decisions before producing the remaining interface screens and animation.

Assign responsibilities across the client, agency, stand builder and multimedia team: who supplies data, prepares hardware, approves copy and accepts integration? For exhibition software, these decisions set the development and testing scope. Compare changes with the work included in the budget so that additional journeys receive an explicit estimate.

Sign off the prototype after testing

For prototype sign-off, replace “it looks good and feels easy” with actions and expected outcomes:

  • A new participant can start and complete the main journey.
  • Cancellation and inactivity return the system to its agreed state.
  • A delayed external response produces an understandable message.
  • The next session starts without the previous participant's data or unfinished actions.
  • An agreed restart restores the required materials and settings.

Run these checks on the target equipment, recording the prototype version, results and remaining limitations. Use the findings to plan the instructions the stand team will need for startup, a normal reset and requesting help. Further production can proceed when the main transitions are clear, critical dependencies have been tested, and unresolved questions have owners and a route to resolution.