In partnership with Google, Sparks built the visual system as one continuous design language across all three Keynotes — a single motion grammar, a single typographic logic, a single approach to translating cloud concepts into image. A team of 60+ designers, motion animators, and producers operated as one production unit alongside the Google Cloud team. The result was a Keynote program that read as one editorial voice, even as the speakers, audiences, and announcement density shifted from morning to afternoon.

A canvas built for distance and density

The primary screen carried the wingspan of a Boeing 737 and a height taller than football field goal uprights. Every visual decision keyed off that scale. Typography sized for a fifth-row read had to hold at the back of the arena. Motion that played as elegant at desktop scale read as chaotic on the canvas — so the system was rebuilt for the surface. The screen was treated not as a backdrop for speakers but as the primary storytelling instrument; speakers and stage architecture were composed to it.

One visual grammar across three Keynotes

Sparks established motion design guidelines that governed the General Keynote, General Session, Developer Keynote, and Partner Keynote as a single editorial system. Consistent transitions. Consistent ways of rendering data, product diagrams, customer logos, and AI concepts. The CXO audience and the developer audience saw the same visual language at different altitudes — strategic frames for the General Keynote, architectural and code-level frames for the Developer Keynote — but the through-line held.

A complete graphics package

The package extended beyond hero moments into every frame of the production: speaker walk-ons, lower thirds, holding slates, in-presentation transitions, demo cues, and announcement reveals. 1,073 screen files, including 778 unique elements, were built and managed across the program. Each was sized, formatted, and timed for the canvas and the run-of-show.

Translating the abstract

Cloud computing, AI, and infrastructure are categories that resist easy visualization. Sparks partnered closely with the Google Cloud team to translate complex concepts — compute, model architecture, data flow, security posture, partner ecosystem — into dynamic visuals built to land with developers without losing CXOs. The translation work was the design work.

Production at hyperscale

The system pushed 10TB+ of content per day and more than 10 trillion pixels across the run. The pipeline was built for it: revision, approval, render, and showfile management operated as one workflow with the Google Cloud team, with version control and on-site adjustment capacity built in for live updates between sessions.

The program landed on three outcomes that matter to brand and revenue leaders:

One story, three audiences.
The Keynote system addressed CXOs, ITDMs, and developers within one continuous visual language — collapsing the usual gap between strategic and technical communication at enterprise tech conferences.

The screen as instrument.
A canvas at 737-wingspan scale is a production challenge most programs treat as a constraint. Here it became the storytelling lead — the surface that made 260 product announcements feel like one argument.

A production system built for the platform.
10TB per day, 10+ trillion pixels, 1,073 files, 60+ people operating as one team — a workflow built to match the scale of the company hosting it.

Google Cloud Next is the product of many hands. Google Cloud led the program's vision, content direction, and product narrative. Sparks served as the lead content and visual design partner for the Keynote program — establishing the motion design guidelines, leading the visual storytelling, design, and animation across the General Keynote, General Session, Developer Keynote, and Partner Keynote, and producing the complete graphics package that ran across the surface.

The broader Next program is built by a wider ecosystem: venue and AV operations at Mandalay Bay, production crews, technical staging partners, and the Google Cloud teams across product, marketing, and developer relations who shaped the announcements themselves. Sparks's work sits within that ecosystem — bounded to the Keynote content layer, integrated with everything around it.