This will sound blunt because it needs to. If you are not qualified to lead AI in a real company, do not take the speaking event. An AI rookie with a polished deck can do more damage in forty-five minutes than a bad software vendor does in a year — because the room will treat your confidence as a map.
I have spent twenty years and more than a thousand stages learning what rooms actually need. Zero recycled keynotes is not a brand flex. It is a safety practice. Wrong urgency, wrong tools, wrong “just automate everyone” advice — people go home and break things.
What does “qualified” mean here?
Not “I use ChatGPT.” Not “I read the newsletters.” Qualified means you have operated through the ugly middle: permissions, bad data, change management, evals, the night the agent books the wrong job. It means you can answer infrastructure questions without sliding into vibes — behind the curtain. It means you know the difference between expert and novice when the label is on your own badge.
When a rookie speaker does damage
- They freeze fear into strategy. Doom without a path — or hype without grief — so teams either panic-buy or shut down ( scared and all in is the honest register).
- They sell tools as transformation. Zaps and copilots get called “agentic,” and the company stops climbing the maturity ladder.
- They teach theater. The room leaves applauding and Monday looks the same — except now leadership thinks they “did AI.”
What program committees owe the room
Due diligence. Ask what the speaker runs. Ask for a failure. Ask whether they will customize for your tools or recycle last month’s deck. Ask fees and booking path in the open — ours are published — so the incentive is not mystery.
The room is often already ahead of the stage — that essay. Your job is not to find the loudest novice. Your job is to find an operator who will not waste the room’s courage.
Proof — and the standard I hold myself to
I still get scared. I still publish dates so you can grade me (Prediction Ledger). I still rebuild decks because the room’s stack changed. If I ever treat your conference like a content-marketing channel for advice I would not run inside CI Web Group, I should lose the slot. Hold me to the receipts.
The damage is not abstract
I have watched rooms leave with "AI will replace your techs next year" as if it were a plan — and watched owners freeze hiring while a competitor industrializes follow-up. I have watched "just buy this tool" become a six-month distraction from data and permissions. Wrong certainty is not inspiration. It is operational debt with applause on top.
If you are early in your own rebuild, teach small rooms. Publish essays. Sit on panels where you can say "I do not know yet." Do not take the keynote slot that will be quoted as gospel by people who cannot afford your learning curve.
Program committees: put "operator receipts required" in the RFP. Ask for a failure story with a date. Ask whether the deck will be unique to your room. If the speaker balks, you just protected your audience from a expensive story hour.
Audiences: you are allowed to ask hard questions from the floor. "What do you run?" "What broke?" "What would prove you wrong by December?" If the answers are fog, do not implement the talk. Clap politely if you must — then go build with people who open the curtain.
Action
Speakers: decline the mic until your scars are real. Coordinators: put infrastructure questions in the booking brief. Owners in the audience: if the talk cannot survive one curtain question, do not bring it home as strategy. If you want the standard on your stage, book Jennifer or grab the speaker kit. For what rooms actually need, read What a Thousand Stages Taught Me.