← All work

Event platform & event design

Aston Martin

The console that ran Masters in Conversation, and the event around it, for the launch of 007: Road to a Million.

Role
UX/UI Design Lead · Event design
Client
Aston Martin · Prime Video · EON Productions
Platform
Web app · Event & social design
Team
Design team of 3, project managers, executives, technical leads, developers, marketers

At a glance

  • 1M+campaign impressions
  • 3brands in one approval flow

Challenge

A launch evening for three brands at Q New York, usually run on scattered spreadsheets and email threads.

Approach

Masters Console, the web app that runs the evening end to end, plus the event identity: social, LED stage, print.

Result

One source of truth for every team, a repeatable format and 1M+ impressions.

01

The problem

Aston Martin launched Masters in Conversation, a new symposium series, at Q New York, its home on Park Avenue, timed with the premiere of 007: Road to a Million with Prime Video and EON Productions. One evening had to carry three brands at once, and feel as precise as the cars on display.

Behind the stage sat the harder problem. Guest lists, approvals from three brands, seating, suppliers, stage cues and arrivals were spread across spreadsheets and email threads, each owned by a different team.

Every team needed the same evening from a different angle: the event lead the whole picture, partners only what they had to approve, the door team only who was arriving, the operator only the next cue.

Scope · one evening, four fronts, three brands

01Main focus
Masters Console

The platform that runs the evening: guests, approvals, seating, run of show, show control, check-in.

02
Event identity

Lockup, waveform motif, type and colour, shared by stage, print and the console.

03
Social campaign

Teaser, reels, feed posts and stories, before, on the day and after the event.

04
On-site assets

LED stage backdrop and screen cues, wayfinding, table and menu cards.

Signed off byAston MartinPrime VideoEON Productions
Fig. 01Scope: the platform first, with the identity, social and on-site design around it
02

My role

Role

UX/UI Design Lead · Event design

The whole project ran through Octonano. I led the design end to end within a design team of three: the platform, from information architecture to dev-ready UI, and the whole event design, from social to the assets on site. Day to day I worked with project managers, executives, technical leads, developers and marketers, turning each team's needs into one shared tool and one visual language.

Worked with

  • Design team of 3
  • Project managers
  • Executives
  • Technical leads
  • Developers
  • Marketers

What I owned

  1. 01Platform IA, UX and UI
  2. 02Dev-ready specs with the developers
  3. 03Event identity and LED stage visuals
  4. 04Social campaign: teaser, reels, posts, stories
  5. 05Print and on-site signage
  6. 06Alignment across three brands
Fig. 02Who I worked with, and what each group needed
03

How I approached it

I started from the evening itself, walking the run of show minute by minute with project managers and technical leads, and mapping who needs what, and when. That became the console's structure: one shared data set, a view per role, and three phases: planning, show night and wrap-up.

Approvals were the critical path. Every guest batch, press line and screen asset needed a yes from Aston Martin, Prime Video and EON Productions, so each item shows the three brands side by side, with who is still waiting.

On the night, the same data switches to live views: front of house checks guests in, show control fires the LED cues, and the event lead sees who is in the room and what comes next.

Key decisions

  1. 01One data set, a view per roleEach team sees only what it needs: less noise, fewer mistakes.
  2. 02Three phases: planning, show night, wrap-upOne console changes its job through the evening, no tool switching.
  3. 03Three brands side by side on every approvalWho approved, who asked for changes, who still has to reply, at a glance.
  4. 04Run of show linked to the LED cuesStage and schedule never drift apart.
  5. 05One visual language from console to stageThe console shares the event's colour, type and waveform.
WIREFLOW · ONE CONSOLE, THREE PHASES, A VIEW PER ROLEPLANNINGSHOW NIGHT · WRAP-UP01 Guests & RSVPInvites, replies, tiersEvent lead · Marketing02 ApprovalsThree sign-offs per itemAston Martin · Prime Video · EON03 Venue & seatingSeating plan, by tableEvent lead04 Run of showA cue for every momentEvent lead · Tech leads05 LogisticsSuppliers, cars, printEvent lead · PMs06 Check-inFind, check in, seatFront of house07 Show controlPreview, take, fadeShow control08 Live overviewWho's in, what's nextEvent lead · Executives09 Results & follow-upReach, attendance, leadsWrap-up · Marketing?Signed byall three?YesNo · changes requested, the item reopensEdge case A confirmed guest has no seat → flagged on OverviewSystem Every approval closed → show file locked, each role switches to its show-night viewIN PARALLELlive dataWrap-upEdge case A VIP arrives → their host is told who to meetEdge case Auto-follow off → timed cues wait for a manual Take↺ Setup reused for Episode 02ScreenKey step: three-brand approvalsDecisionSystem eventEdge caseFork / joinWho actsFlowLoop back
Fig. 03Low-fidelity wireflow: planning, show night and wrap-up across roles
RUN OF SHOW · ONE EVENING, THREE ZONES, ONE CLOCK4 PM5 PM6 PM7 PM8 PM9 PM10 PMClose 10:30 PMLED cuesStage screenQ1Q2Q3Q4–6Q7Q8Q9Q10Q11StageShow control · AVGalleryCars · diningArrivalFront of houseCrew call & tech check4:007:15 Welcome7:25 Teaser & trailer premiereConversation7:35Q&A8:20Cars inposition5:00Reception6:30Dinner among the cars8:40Briefing5:30Doors open6:30Farewells & gifts9:45MomentMasters in Conversation, 45 min on stageFull blackout for the premiereScreen cue, fired from Show control
Fig. 04Run of show: the evening by zone, with every screen cue
12345
  1. 1Three brands side by side, each with its own status
  2. 2Deadlines turn red on the day they fall due
  3. 3A change request sits inline, in the partner's own words
  4. 4One tap reminds whoever is still waiting
  5. 5Aston Martin approves in place, with no email loop
Fig. 05Approvals: three brands, one view
12345
  1. 1Programme clock, what's in the room now and the next cue
  2. 2Preview and program, like a broadcast desk: load, check, take
  3. 3Take, fade, black: three actions, sized for a tense moment
  4. 4Auto-follow fires timed cues; off, every cue waits for a Take
  5. 5Cue list linked to the run of show, row by row
Fig. 06Show control on the night: a broadcast desk for the stage LED
04

What I built

Masters Console was built with the developers from my dev-ready specs: nine views, from guest list to show control, on one data set. Around it I designed the event's identity and every touchpoint: the teaser and social campaign, the LED stage backdrop, print and signage.

  • Overview with live timeline
  • Guest list, tiers and RSVP
  • Three-brand approvals
  • Venue & seating plan
  • Run of show with LED cues
  • Show control: preview, take, fade
  • Logistics: suppliers, cars, print
  • Front-of-house check-in
Overview · planning
01Overview · planning
Approvals · three brands
02Approvals · three brands
Guest record & host brief
03Guest record & host brief
Run of show
04Run of show
Venue & seating
05Venue & seating
Logistics
06Logistics
Show control · live
07Show control · live
Check-in · front of house
08Check-in · front of house
Fig. 07Masters Console on iPad, from planning to show night

Type · Flare for display, Inter for the interface

Page titleOVERVIEWFlare Regular 400 · 16 px · caps · 0.3em
MomentMasters in ConversationFlare Regular 400 · 25 px
KPI121 / 140Flare Regular 400 · 34 px
SectionBefore doors openFlare Medium 500 · 17 px
EyebrowEPISODE 01 · Q NEW YORKFlare Medium 500 · 11 px · caps · 0.24em
ParagraphFour chairs, one question.Inter Regular 400 · 14 px · 1.45
MetaDue today · waiting on Prime Video and EONInter Regular 400 · 12 px · muted
Button · statusRun of show · ConfirmedInter Medium 500 · 12.5 / 11.5 px

Flare is Aston Martin's brand typeface, shown here in a close stand-in.

Colour

Racing#00695FDeep#00483FTeal#4FA393Mist#7FBCB5Champagne#B39B6EPaper#F1F4F2

Status · same colours for guests, approvals and cues

ConfirmedAwaiting replyChanges requestedLive on stage

Components

PlanningShow nightWrap-upVIPRun of showTake
Lockup · LED · social

Masters in Conversation

Fig. 08Design system: type scale with weights, colour, status and components, shared by console, stage and social
Fig. 09Social campaign: story, teaser reel and feed post
Fig. 10Series teaser, cut for the stage LED and partner channels
05

The result

  • 1M+campaign impressions
  • 3brands in one approval flow

Masters in Conversation launched as a series, not a one-off. Episode 01 ran from one console shared by every team, and the campaign generated over 1M impressions across partner channels.

The setup was designed to be reused: guests, run of show and cues from Episode 01 become the starting point for the next episode.

On stage at Q New York, in front of the LED backdrop
Fig. 11On stage at Q New York, in front of the LED backdrop
The Q New York lobby, with the DB5 on display
Fig. 12The Q New York lobby, with the DB5 on display
Details on display through the evening
Fig. 13Details on display through the evening

Contact

Let's build something people use and businesses need.