Engineered to Outrun

Read the campaign story

ABB announced Engineered to Outrun on 31 October 2024 as a new positioning around electrification and automation. The company described the work as involving corporate teams, business divisions and customers. Its announcement established the intended meaning of the platform rather than reporting a measured change in how customers perceived or used the company’s technology.

A 2025 production case documents a film expression using virtual environments for settings including a city, factory and racetrack. Gorodenkoff’s account gives specific agency, production and directing credits. That later film belongs to the same platform, but its creators are not assumed to have developed the original positioning. Cinematic settings do not independently demonstrate the performance of the systems they represent.

Editorial interpretation: an action word can give a broad industrial portfolio a common direction without requiring every product to look alike. The challenge is to translate that action into a relevant meaning for each audience. A buyer concerned with continuity, for example, may understand performance differently from someone considering resource use. The umbrella should help organise those explanations rather than suggest that every application improves every dimension at once.

Editorial interpretation: virtual production can make an otherwise fragmented range of environments feel like one coherent world. That is a communication choice, not proof that the depicted systems were operating together or that the production itself had a lower environmental footprint. A responsible adaptation should preserve the distinction between illustration and observation. The film can create an invitation to investigate while the practical evidence remains available in a separate, clearly scoped explanation.

Define the action in the audience’s terms

Translate the brand verb into the specific job a customer is trying to accomplish. Ask what observable change would matter and which conditions affect it. Avoid making the same broad promise mean everything to everyone. A shared platform becomes useful when different teams can explain their contribution consistently while still acknowledging the distinct constraints, trade-offs and evidence associated with each application.

Treat visual scale as an editorial choice

A seamless journey through several environments can imply breadth, but it should not imply that every scene records a real deployment. Label illustrative material where needed and avoid attaching unsupported performance claims to spectacular settings. Review what a viewer believes happened in the real world. This helps the team preserve cinematic ambition without allowing the production method to substitute for product validation or customer evidence.

Keep the platform and execution credits separate

A long-running positioning may involve different teams at different stages. Record who developed the strategic platform and who produced each later film or activation, rather than assigning the most visible agency every role. The same discipline helps with dates and claims. It prevents a later case film from silently becoming the origin story and makes the library more useful to teams studying how strategy turns into execution.

A small test for another brief

Proposed adaptation: storyboard one fictional maintenance-planning service across three illustrated work settings, using a shared action while giving each setting a distinct practical explanation.

Measure whether participants understand the shared role and the differences between applications. Ask which scenes they believe show real operating evidence, then revise any misleading impressions. Evaluate comprehension rather than assuming that cinematic scale establishes technical competence or sustainability.

Stop if illustration is mistaken for a verified deployment or the campaign implies unsupported comparative, safety or environmental performance.

• Use original diagrams rather than simulated safety-critical operations.
• Label every scene as illustrative and state service limitations.
• Separate the umbrella promise from the facts attached to each example.