What separates a good keynote from a great one?

The best producers I know are covered in scars.

No, not literally. But you can’t cook, or learn to cook, without getting burned. When you produce long enough, you have a tapestry of things that, on one hand, you wish you could take back, and on the other hand, you know you wouldn’t be the producer you are if you hadn’t been burned while learning to cook.

If you sit with them long enough, over a meal the night before a show or in the debrief after something went sideways, you start to understand that their competence isn’t a collection of techniques they learned. It’s a sediment of mistakes, some small, some expensive, some that kept them up for weeks. That sediment becomes the bedrock of their character. And the ones who are truly great don’t make the same mistake twice. That’s not a small thing. That’s the whole thing.

I say this because when companies come to us looking for a production partner for a keynote, a broadcast, a high-stakes flagship conference, an executive moment that needs to land, the conversation almost always centers on capabilities. Can you show me some designs? What’s your process? What does your team look like? These are reasonable questions. But they’re not the right questions.

Here’s what it’s cost me. And what I learned.

Years ago, I took on a show, a client, that was more ambitious than the budget could actually support. I knew it was ambitious. I believed in the vision. I thought we could make it work.

We couldn’t.

Not within their budget allocation. And when the final accounting came in, I had to sit across from a client I genuinely respected, adored really, and own that I had gotten lost in the potential and undercommunicated the risk. There’s no graceful version of that conversation. You offer contrition. You accept the discontent. And you leave with a lesson that no course, no book, and no colleague could have given you.

The lesson isn’t simply “budget more carefully.” The lesson is that ambition without fastidiousness is just wishful thinking with a production schedule attached. The producer’s job isn’t to believe in the show. It’s to believe in the show and hold the line, to be the person in the room who loves the vision and also tells you honestly what it costs. When those two things come apart, everyone loses. On the client side, missing a budget can have reputation consequences or lead to a loss of work. On the agency side, trust.

I have not let a budget conversation go undercommunicated since. Every assumption is checked. Every risk is flagged. The client may not always love what they hear, but they know exactly what they’re buying.

Here’s a smaller scar, but in some ways a sharper one.

I was working with a young technical director, genuinely talented, newer to this scale of show, and he came in with a load-in plan. Scheduled to the hour. Thoughtfully sequenced. It was a good plan.

I second-guessed it. Not dramatically. I didn’t overrule him or tear it up. I just… butted in. I was young too, and insecure, and I let the doubts set in. I spoke to vendors. Offered adjustments. Pulled on threads. In doing so, I broke the chain of communication he’d built with the team and introduced ambiguity into a process that had been clear.

The load-in went fine. But it would have gone better if I had stayed out of it. I know this because I watched what happened in the moments where my adjustments took hold, and I watched what happened in the moments where his original plan did. He was right. I was noise.

The lesson isn’t simply “trust your people,” though that’s true. The lesson is that undermining a plan, even gently, even with good intentions, breaks something subtle but real. His crew was running on his logic. When I introduced mine, I made everyone do extra cognitive work in a moment when they needed to be on autopilot. The other lesson: if you have questions or doubts, review the plan again. Hear the explanation. Absorb the logic. Stay observant. But trust your key leads until they give you a reason not to.

So, what does this have to do with your event?

Everything, actually.

A keynote is a system: narrative, performance, technology, timing, and human beings under pressure. Systems of that complexity do not respond well to producers who are still learning from their first expensive mistakes on your stage. That’s the reason experience matters more than the resume. It’s the pattern recognition that only comes from having been in rooms where things went wrong and figuring out, in real time, how to hold it together, or how to prevent it next time.

When you’re evaluating who to trust with your keynote, broadcast, or event, anything with a lot of moving parts, don’t just ask about the wins. Ask about the mistakes. Ask what they’ve gotten wrong and how it changed the way they work. Ask what they would have done differently on a show that looked, from the outside, like it went fine.

A producer with no good answer to that question either hasn’t been cooking long enough, isn’t being honest, or hasn’t been paying attention.

The scars are the credential. Everything else is just equipment.