Before the Speaker Arrives

Send the audience brief, the room plan, and the technical facts early. Ask back for the introduction exactly as it should be read, the talk assets, and the pre- and post-event resources the room will receive. The Event Playbook features in this magazine show what that exchange looks like when it is done well.

The argument of this piece is that a talk is substantially decided before the speaker arrives, in an exchange of documents most planners treat as administration. It is not administration. It is the production itself, conducted on paper, and its quality sets the ceiling on everything the audience will experience. A speaker who receives the audience brief early writes a different, better talk: aimed at the room that actually exists, pitched at its level, armed with its examples. A speaker who receives nothing until the sound check performs a generic talk competently, and the audience can tell the difference within ten minutes, even if it cannot name it.

Consider what each document actually does. The audience brief tells the speaker who is in the room: roles, seniority, what they are worried about this year, what they have already heard from the last three speakers on this circuit. The room plan tells the speaker what the space will permit: stage geometry, screen placement, whether the audience can see each other, whether there are tables for writing or rows built for watching. The technical facts are the contract against surprise: microphone type, clicker, confidence monitor, who runs the slides, what happens when the video fails. None of this is glamorous. All of it converts directly into the talk's quality, because a speaker prepared on these three documents spends the performance on the room instead of on the conditions.

The return half of the exchange matters just as much, and it is the half planners most often receive late or not at all. The introduction, exactly as it should be read, protects the talk's first two minutes from an emcee's improvisation. The talk assets, slides and media in final form, protect the technical run from version chaos. The pre- and post-event resources determine whether the talk has a half-life: what the room reads before it arrives, and what it is handed to continue with after. Asking for these early is not fussiness. It is how a planner discovers, weeks in advance, which speakers run a professional operation and which ones intend to improvise at the audience's expense.

One item in the technical facts deserves its own sentence, because it separates professionals from performers: the failure plan. What happens when the video will not play, when the microphone dies, when the slides freeze on the third pillar? Every experienced speaker has a rehearsed answer, and the answer is a talk that can survive its own equipment. Ask the question early, in the production exchange, and listen for ease. The speaker who has planned for failure will describe the fallback without defensiveness, the way a pilot describes a checklist: as a normal part of the work. The speaker who treats the question as an insult is telling you how the event day will go if anything slips.

A worked example from the founding issue

The founding issue's Event Playbook feature follows Justin Maxwell's "Business Wealth to Generational Wealth," and the playbook treatment is precisely this exchange, examined step by step. The talk's problem is a hard one to land: business owners who believe the income they have built is the asset, when the talk's first pillar insists income is not the asset at all. Material like that, valuations, systems, an exit the owner controls, tax and estate planning that survives the handoff, cannot be pitched generically. It has to be aimed: at owners of a certain scale, in a certain posture toward their businesses, seated in a room set for working rather than watching. The playbook exists because the preparation is part of the product; the audience brief is where the speaker learns whether the room holds owners near an exit or owners a decade from one, and the talk is built differently for each. Behind the Talk makes the same point from the other side of the stage, following Bobby Dutton's preparation for "Rise Above the Noise": pre-flight discipline, rehearsal treated as simulator time, decisions made calm at altitude. His first pillar is checklist discipline before the pressure arrives. It is a talk about preparation, prepared the way it teaches.

The committee checklist

• Send the audience brief when the contract is signed, not the week of the event: roles, worries, and what the room has already heard.
• Send the room plan with geometry: stage, screens, seating, and whether the audience can see and reach each other.
• Send the technical facts in writing: microphones, clicker, monitor, slide operator, and the failure plan.
• Require the introduction verbatim, exactly as it should be read, with pronunciation notes.
• Require final talk assets by a date certain, and freeze versions after it.
• Agree the pre-event resource the room receives and the post-event resource it is handed to continue with.
• Hold one production call whose only agenda is this exchange, and treat a missed document as a signal, not a detail.

None of this requires budget. It requires treating the weeks before the event as part of the event, which they are. The audience will never see the audience brief, the room plan, or the call where the introduction was worded. It will simply experience a talk that fits its room like it was built there. It was. It was built there on paper, by the planner and the speaker together, before the speaker arrived.