Anton Woodward
I’ve often said that the best stage automation is barely noticeable. It moves the story along and does not draw attention to itself.
In most production meetings, my focus is straightforward: weight, speed, safety, synchronisation, noise and repeatability.
-
- How much does it weigh?
- How fast does it need to travel?
- Can it be delivered safely?
- What does it need to stay in sync with?
- Will motor noise be an issue?
- Will it do it reliably, eight times a week?
Those questions define the work.
Over time, I’ve found that the answers to them influence more than engineering performance.
Speed is an obvious example. A revolve running marginally slower can extend a moment; slightly faster, and it pushes energy forward. The numerical difference may be small, but on stage the effect is clear.
Mass and perceived weight also matter. A large piece of scenery moving with visible effort reads differently from a lightweight element travelling quickly. Even when audiences are not consciously aware of it, they respond to it.
Noise is similar. Reducing mechanical sound changes how movement sits within a scene. The same cue, executed more quietly, becomes part of the background rather than a focal point.
Synchronisation is critical. When motion lands precisely with lighting or music, it feels resolved. When it is fractionally adrift, it can unsettle rhythm and focus.
None of this alters the primary responsibility of automation. Systems must be safe, predictable and repeatable. Without that foundation, there is no room for nuance.
But once scenery moves in front of an audience, it affects pacing and perception whether we discuss it in those terms or not. Decisions about speed, control and behaviour have consequences beyond mechanics.
If automation is doing its job properly, it supports performance and keeps the story moving.
At its best, it is barely noticeable.