Field Notes // Programme

What 10 Editions Of ACSS Taught Us About Programming Keynotes

By CGD Group Programme & Speakers 6 min read

Ten editions of the Annual Cyber Security Summit is a lot of keynotes — hundreds of speakers, thousands of slides, and a 500-person room that tells you within ninety seconds whether you got it right. These are the lessons that survived contact with that room.

01

Book operators, not job titles

The biggest name on the flyer is rarely the talk people mention at dinner. The sessions our delegates rate highest, year after year, come from people who run things — incident commanders, CISOs who have lived through a breach, engineers who built the tooling they're describing. A senior title fills seats; an operator keeps them filled after the coffee break.

So when we programme a keynote slot, the first question isn't "how senior?" — it's "what have they actually done that this room hasn't?"

02

One idea per keynote

The 60-slide company deck is where keynotes go to die. The talks that land at ACSS make one argument, prove it with one war story, and leave one thing the audience can do on Monday. Everything else is appendix.

That discipline doesn't happen by accident — it happens in the speaker briefing. We brief hard, weeks out: here's the room, here's who's in it, here's the one question your slot exists to answer. Speakers thank us for it afterwards. So do their audiences.

03

Protect the morning

Energy is a budget and the morning is when you're richest. We put the hardest, densest content before lunch and never apologise for it. After lunch belongs to formats that generate their own energy — panels with real disagreement and live demos. A deep technical lecture at 2:30pm isn't brave programming; it's a donation to the hotel's coffee bill.

A 500-person room tells you within ninety seconds whether you got the keynote right.
04

Treat live demos as managed risk

Nothing wins a technical audience like a live demo — and nothing loses one like a demo dying on stage. We treat demos the way operators treat production changes: rehearsed on the actual stage hardware, on the actual venue network, with a recorded fallback ready on the switcher. The speaker gets to be fearless because we've already planned for the failure.

05

A sponsored keynote is still a keynote

Stage time is part of what our sponsorship packages include — and the lesson from ten editions is that a sponsored slot only works when it's held to the same bar as every other slot. The moment a keynote becomes a product brochure read aloud, the room checks out — and the sponsor gets the worst possible return on the best slot we sell.

So we work with sponsor speakers the same way we work with everyone: one idea, real stories, brief hard. The sponsors who lean into that are the ones who get renewals' worth of pipeline from a single talk — and the audience never has to reach for their phone.

06

End pointing at the hallway

The keynote isn't the product. The conversation it starts is. The best closers we've programmed end with an open question, a challenge, or a name-check of who else in the room is working on the problem — anything that hands momentum to the hallway, the expo floor, and the networking that the whole summit is actually for.

Ten editions in, that's the real job of a keynote at ACSS: not to fill forty-five minutes, but to give five hundred people something worth talking about for the rest of the day.