Category: Production & Tech

  • The 10-Minute Rule: Webinar Engagement That Stops Drop-Off

    The 10-Minute Rule: Webinar Engagement That Stops Drop-Off

    The average webinar attendee watches for about 29 minutes. The average B2B webinar runs 45 to 60. Sit with that gap for a second — it means the back third of your deck, usually where the demo and the offer live, plays to a room that has already half-emptied. Across a thousand-plus enterprise webinars, the sessions that held their audience to the end were never the ones with the prettiest slides. They were the ones where the audience had a job to do.

    That is the entire playbook in one sentence: never let ten minutes pass without asking attendees to do something. Below is how I run that rule in practice — the poll questions that actually get answered, the chat prompts that beat “drop your questions anytime,” and a minute-by-minute engagement map for a 45-minute session you can steal outright.

    The 10-minute rule, explained

    Attention in a webinar does not fade evenly — it decays in the gaps between tasks. Give someone twelve uninterrupted minutes of slides and the second monitor wins. So the rule I hold every producer to is simple: an interactive element at least every ten minutes, and in practice we aim for every seven or eight. Sessions that combine polls with active chat run roughly 22% higher on engagement measures than broadcast-style sessions, and you can feel that difference from the presenter’s chair.

    What counts as an interactive element matters, though. It has to be a specific ask with a specific answer format:

    • A poll with 3–5 options, whose results you read aloud and act on.
    • A chat prompt with a format. “Type 1, 2, or 3” outperforms “thoughts?” every single time.
    • A Q&A checkpoint — pausing to answer two questions mid-session, not saving everything for the end.
    • A direction vote. Let the room choose which of two examples you walk through next.

    What does not count: “feel free to drop questions in the chat anytime.” That is wallpaper. Nobody acts on an open-ended standing invitation, and you already know this because you have sat through webinars that used it.

    Where your webinar drop-off rate actually comes from

    Before you can fix drop-off you need to know where it happens, and it is not random. In our programs the curve has three cliffs. The first is minutes one through five — people confirming the session is worth their time. If your first five minutes are housekeeping, agenda slides, and a speaker bio, you are paying your churn tax up front for nothing. The second cliff is the halfway mark, where attention dips even in good sessions. The third comes right after the audience senses the teaching is over and the pitch is starting.

    Two planning consequences follow. First, your best material goes early — with average watch time around 29 minutes, content placed after minute 30 is a bonus track, not the album. Second, engagement elements should cluster at the cliffs: a chat prompt in minute one, a recap and vote at the midpoint, and a CTA delivered before Q&A rather than after it. For context on what a healthy funnel looks like upstream of all this, live show-up in our programs lands between 35–50% of registrations, dropping to 25–35% with colder audiences — so the people who did show up are your warmest asset of the quarter. Losing them to an agenda slide is self-inflicted.

    The minute-by-minute engagement map (45-minute session)

    This is the artifact I wish someone had handed me a thousand webinars ago. The 45-minute length is deliberate — it is the sweet spot we keep landing on for B2B audiences — and no gap between interactive elements exceeds ten minutes.

    MinutesWhat happens on screenEngagement element
    0:00–0:02Cold open — state the payoff in one sentence, no housekeepingChat prompt: city + one word for your biggest headache with the topic
    0:02–0:05Frame the problem with one hard numberPoll 1 — diagnostic: which option describes your current setup
    0:05–0:14Teaching block one — your strongest material, not your warm-upRead Poll 1 results aloud; tailor the examples to the winning answer
    0:14–0:15CheckpointPoll 2: which of these tactics have you already tried
    0:15–0:24Teaching block twoCall out two chat comments by name; moderator seeds one question
    0:24–0:26Halfway recap — three bullets, sixty secondsChat vote: which bullet deserves more depth — type 1, 2, or 3
    0:26–0:34Deep-dive on the winning vote, worked example on screenThe vote itself is the engagement — honor the result visibly
    0:34–0:36CTA — one link, one next step, before Q&AModerator drops the link in chat while you talk
    0:36–0:44Q&A — the segment 82% of attendees rate most interestingModerator batches and prioritizes; host answers 4–6 questions
    0:44–0:45Close — restate the CTA, preview the follow-up emailExit poll: want the template, yes or no

    Notice the CTA sits at minute 34, before Q&A. Run it after and a third of the room never hears it. If you want the wording itself dialed in, I keep a running file of webinar CTA examples that convert — placement gets you heard, phrasing gets you clicked.

    Webinar poll questions that get answered

    Most webinar poll questions fail because they are trivia — “what year was Zoom founded” energy. A poll earns its interruption when the answer changes what happens next, or tells attendees something about the room they cannot see. Three polls in 45 minutes is the right dose; more and they blur into noise.

    • The diagnostic. “Which best describes where you are today?” — four stages, no jargon. It segments the room and tells you which examples to lean on.
    • The experience check. “Which of these have you tried?” — sets up your next block as either introduction or correction.
    • The commitment close. “Want the template we just walked through?” — a yes/no that doubles as a hand-raise for follow-up.

    The non-negotiable: read the results aloud and do something with them. A poll you launch and never mention again trains the room that participation is decorative. Say the number, name the majority, adjust the next five minutes to match. That loop — ask, acknowledge, adapt — is the mechanism behind that 22% engagement lift, not the poll widget itself.

    Chat and Q&A: the highest-leverage tools you already own

    Attendees consistently rate Q&A the most interesting part of a webinar — 82% in the research, and my own exit surveys agree. Which makes it strange that most hosts treat it as a buffer: three rushed minutes at the end, answered to a departing room. Budget eight minutes for it, place it after the CTA, and staff it properly.

    Properly means a moderator. Someone other than the presenter watches chat, batches duplicate questions, flags the good ones, and — critically — seeds the first question, because nobody wants to go first. The mechanics are the same ones I use for panels, and they are covered in detail in my guide to moderating a webinar panel. One more habit worth stealing: use names. “Sarah asked exactly the right question here” costs nothing and signals to every listener that the room is live, not a recording.

    The halfway recap — your cheapest retention win

    Attention reliably dips at the midpoint. My fix is a sixty-second recap at minute 24: three bullets on one slide, then a chat vote on which one gets the deep-dive. It works on three levels at once. It rescues anyone who zoned out — they can rejoin without feeling lost. It converts passive listeners into voters. And it hands you a natural edit point for the replay, which matters more than most hosts think, because replay viewers typically match or exceed your live audience. A recap that re-anchors a live viewer at minute 24 does the same for a replay viewer who is skimming.

    When the format should do the work for you

    Everything above assumes a presenter-led session, which is the hardest format to keep alive — you are fighting the medium. Sometimes the smarter move is picking a structure where interaction is the content: an AMA has no drop-off cliff because the audience is steering, and a hands-on workshop keeps people because leaving means losing their work-in-progress. I compare these in my breakdown of AMA and workshop webinar formats, including when each one beats a standard presentation.

    And remember that engagement is a means, not the scoreboard. A session that holds 80% of the room but generates no next step still failed. Every tactic here is meant to earn the right to a follow-up — that part of the system lives in the webinar follow-up playbook.

    Frequently asked questions

    How do you keep webinar attendees engaged?

    Schedule interaction instead of hoping for it: an interactive element — poll, formatted chat prompt, Q&A checkpoint, or direction vote — at least every ten minutes. Front-load your best content into the first half hour, recap at the midpoint, and give Q&A a real eight-minute slot rather than the leftovers.

    How many polls should you use in a webinar?

    Three in a 45-minute session: a diagnostic in the first five minutes, an experience check near the middle, and a yes/no commitment poll at the close. Each one only counts if you read the results aloud and visibly adjust to them.

    What is a good webinar drop-off rate?

    With average watch time around 29 minutes, holding 60–70% of your peak live audience through minute 40 of a 45-minute session is strong. If you lose more than a quarter of the room in the first ten minutes, the problem is your open — usually housekeeping and bios where the payoff should be.

    How long should a webinar be to keep people engaged?

    45 minutes is the sweet spot for B2B audiences — long enough for two teaching blocks, a worked example, and real Q&A, short enough that finishing does not require heroics. Sixty-minute sessions mostly add content that plays to an emptier room.

    This is lesson-one material from our courses — see what’s coming, or get the free lessons by email as they ship.

  • The 24-Hour Webinar Tech Check (Dry Run Checklist)

    The 24-Hour Webinar Tech Check (Dry Run Checklist)

    Three minutes into a product launch webinar a few years back, I watched a keynote speaker’s audio turn to gravel in front of several hundred live attendees. Hotel Wi-Fi, laptop mic, no backup plan — and we discovered all three problems in production instead of rehearsal. That show recovered, barely, but it changed how my team preps every event since. Across a thousand-plus enterprise webinars, the pattern is boringly consistent: the disasters were almost never platform failures. They were things a proper dry run would have caught 24 hours earlier.

    This is the exact webinar dry run checklist we run the day before every live event. It takes about 45 minutes with all speakers present, and it has quietly prevented more failures than any piece of software we have ever bought.

    Why 24 hours out — not 30 minutes before

    Most teams do their “tech check” in the green room half an hour before going live. That is not a tech check. That is a discovery session for problems you no longer have time to fix.

    The 24-hour window is the whole trick. If a speaker’s mic sounds thin, there is time to courier a USB mic or switch them to a different room. If their upload speed can’t hold a screen share, there is time to move them onto ethernet or pre-record their segment. If the polls were built in the wrong session template — a mistake I have made personally more than once — there is time to rebuild them. Every one of those fixes takes hours, not minutes. Thirty minutes before showtime, your only fix for anything is “hope.”

    One rule we hold hard: the dry run is non-negotiable for every speaker, including the executive who “has done a hundred of these.” Especially that one. In my experience the most senior speaker on the roster is the single most likely person to show up on a laptop mic over conference-room Wi-Fi.

    The full-platform rehearsal

    The rehearsal happens on the same platform, in the same session type, with the same roles you will use live. Not a Zoom call to talk about the Goldcast event. Not a Teams meeting to discuss the Zoom webinar. The actual event environment — because permissions, layouts, and backstage behavior differ between a test meeting and a production webinar session on every platform I have used. If you are still deciding which platform that should be, settle it before rehearsal week — here is our honest comparison of Zoom vs Teams vs the dedicated webinar platforms.

    What we walk through, in order:

    • Entry and roles. Every speaker joins through the real speaker link, not a forwarded calendar invite. Confirm each person lands with the right permissions — panelist, not attendee.
    • Camera and framing. Eyes in the top third of the frame, light source in front of the face, no window behind them. Two minutes of adjustment here is the cheapest production-value upgrade that exists.
    • Slide handoffs. Practice the actual transitions — who advances, who shares, what the handoff cue is. This is where a written run of show earns its keep; every cue in the rehearsal should map to a line on that document.
    • First 90 seconds, out loud. Have the host actually deliver the open. The awkwardness you hear in rehearsal is the awkwardness attendees would have heard live.

    Guest speakers get this checklist in writing at least a week before, alongside their prep call — the full process is in our guest speaker briefing playbook. Speakers who know what to expect show up ready. Speakers who don’t show up on hotel Wi-Fi.

    Audio setup: the one thing attendees never forgive

    Here is the trade I will make every single time: average video, great audio. Attendees will happily watch a slightly soft webcam image for an hour. They will leave within minutes if the audio is echoey, clipped, or buried in keyboard noise. In our post-event surveys, audio complaints outnumber video complaints by a wide margin — it is not close.

    The audio portion of the dry run: each speaker talks for 30 uninterrupted seconds while everyone else listens on headphones and one producer listens on laptop speakers — because that is how your attendees will hear it. Listen for echo (hard-walled room), hiss (gain too high), and plosives (mic too close). Then have them type while talking. Laptop mics pick up keystrokes like a hailstorm.

    You do not need a broadcast studio. This budget kit has covered hundreds of our speakers:

    ItemBudget pickApprox. costWhy it matters
    USB dynamic micSamson Q2U or similar~$70 at the time of writingDynamic mics reject room echo that condensers amplify
    Wired headphonesAny wired earbuds~$15Kills echo and Bluetooth dropouts; wired beats wireless for reliability
    Ethernet adapterUSB-C to gigabit ethernet~$20The single biggest stability upgrade available
    Front lightSmall LED panel or a window in front~$30 or freeFace light does more than any webcam upgrade

    Roughly $135 per speaker, and it outperforms setups costing ten times more that skip the fundamentals.

    Internet and hardware: hardwire or gamble

    Wi-Fi is fine until someone in the house starts a video call, a backup kicks off, or the microwave runs. Hardwired ethernet removes an entire category of failure, which is why it is a requirement — not a suggestion — for every speaker in our programs.

    • Ethernet connected and confirmed. During the dry run, have each speaker disable Wi-Fi entirely for 60 seconds. If the session holds, they are genuinely hardwired. You will be surprised how often they are not.
    • Speed test from the actual machine. 10 Mbps upload is a comfortable floor for camera plus screen share. Test at the same time of day as the live event if possible.
    • Power, not battery. Laptops throttle performance on battery, and a 90-minute event will outlast more batteries than you would think.
    • Close everything else. Slack, Outlook, browser tabs with autoplay. Notifications during a screen share are both a bandwidth problem and an embarrassment problem.
    • Restart the machine the morning of. A fresh boot clears the mystery processes that accumulate over a two-week uptime.

    Polls, screen shares, and the clicks that fail live

    Interactive elements fail more often than audio or video, because they depend on configuration done days earlier by someone who is not in the room. So we launch every single one during the dry run — not “confirm they exist.” Launch them.

    • Fire each poll live. Confirm it appears to a test attendee, not just in the host view. Half of poll failures are visibility failures.
    • Run every screen share. Each speaker shares the exact deck or demo they will use live. Check for font substitutions, missing videos, and the dreaded presenter-notes-on-screen layout.
    • Play any video with sound. Sharing computer audio is a separate checkbox on most platforms and the single most commonly missed setting I see.
    • Test the handout and CTA links. Click them from the attendee view. A typo in a CTA link costs real pipeline and is invisible from backstage.

    The failure drill: who takes over when a speaker drops

    This is the part almost nobody rehearses, and it is the part that separates a professional operation from a lucky one. At some point a speaker will drop mid-sentence — power cut, ISP blip, blue screen. The question is never whether it happens; it is whether the next ten seconds are handled or chaotic.

    In the dry run, we simulate it. One speaker kills their connection without warning, and everyone else executes the plan:

    • The host bridges immediately. A prepared line — “Looks like we lost Maria for a moment; while she reconnects, let me pull up the question several of you asked” — buys two to three minutes without dead air.
    • Slides have a second driver. The producer or host holds a copy of every deck and can advance from their machine within seconds.
    • The dropped speaker knows the re-entry route. Rejoin link pinned in a group text, phone dial-in as the audio fallback, and instructions to rejoin quietly — no on-mic apology tour.
    • The backchannel is off-platform. A text or Slack thread that survives even if the webinar platform itself is the thing that failed.

    The drill takes five minutes. The first time it saves an event — and it will — those five minutes become the best production investment you make all year.

    The final 60 minutes on show day

    If the 24-hour dry run happened, show day is calm by design. The last hour is verification, not discovery:

    • T-60: Producer opens the live session, confirms recording settings, loads polls, and re-clicks every CTA link.
    • T-30: Speakers join backstage. Quick audio spot-check — 15 seconds each, headphones on. Confirm the final reminder email fired on schedule (our four-email sequence, including the at-start “we’re live” send, is laid out here).
    • T-15: Run of show open on every screen. Phones on silent, group text pinned, water within reach.
    • T-5: Quiet backstage. No new information, no last-minute slide edits. Late changes create more failures than they fix.

    Then you go live knowing every switch has already been flipped once in the last 24 hours. That knowledge changes how relaxed your speakers sound — attendees can hear confidence.

    Frequently asked questions

    What is a webinar dry run?

    A webinar dry run is a full rehearsal held on the actual webinar platform with every speaker present, covering audio, video, internet, screen shares, polls, and handoffs — plus a failure drill. It is a working session, not a social call: every element that will be used live gets exercised once before it counts.

    How long should a webinar dry run take?

    Plan 45 minutes for a standard two-to-three speaker event: about 10 minutes on connections and audio, 20 on content walkthrough and handoffs, 10 on polls and screen shares, and 5 on the failure drill. First-time speakers or complex demos justify a full hour. Under 30 minutes usually means something got skipped.

    Should the dry run be on the same platform as the live webinar?

    Yes — always. Rehearsing a Zoom webinar in a Zoom meeting, or a Goldcast event in a Teams call, tests almost nothing that matters. Backstage behavior, speaker permissions, poll mechanics, and layouts differ between session types even within the same vendor. Use the real event environment, ideally a duplicate of the production session.

    What should a webinar tech check include?

    At minimum: speaker entry links and roles, microphone and headphone check, camera framing and lighting, hardwired internet confirmed with Wi-Fi disabled, a live launch of every poll, every screen share run end-to-end, CTA links clicked from the attendee view, recording settings confirmed, and a rehearsed plan for a speaker dropping mid-session.

    Do experienced speakers really need a dry run?

    Experienced speakers need the dry run more than anyone, because they are the most likely to skip prep and improvise their setup. The rehearsal is not about their speaking ability — it is about their mic, their network, this platform’s quirks, and this event’s handoffs, none of which their experience covers.

    This is lesson-one material from our courses — see what’s coming, or get the free lessons by email as they ship.

  • How to Moderate a Webinar Panel Without Losing the Room

    How to Moderate a Webinar Panel Without Losing the Room

    Three panelists, sixty minutes, and a moderator who opened with “let’s go around and have everyone introduce themselves.” Fourteen minutes later the first actual question hadn’t been asked, a third of the live audience had bailed, and the chat had gone quiet. I was the producer on that one, and I’ve watched some version of it happen dozens of times since — panels are the easiest webinar format to book and the hardest to run well.

    Across a thousand-plus enterprise webinars, the panels that worked had almost nothing to do with panelist star power and almost everything to do with moderation mechanics. This playbook is the system I hand to every moderator I work with: the prep call agenda, the question bank structure, the 90-second rule, how to cut off a rambler without making an enemy, and how to close so the last thing the audience hears isn’t a trailing half-answer.

    Why panels drift

    A solo presenter has one failure mode: being boring. A panel has five — long intros, panelists agreeing with each other for an hour, one voice dominating, dead air while everyone waits to see who answers, and a moderator reading questions off a doc instead of listening. None of these are personality problems. They’re process problems, and every one of them is preventable before the session starts.

    The trade-off is real, though: a well-run panel gives you three networks promoting one event and a conversation that feels alive, but it costs you message control. If you haven’t decided whether a panel is even the right call for this topic, read our breakdown of panel vs. solo webinars first. If the panel is booked, everything below is about protecting the room you worked to fill.

    The 30-minute prep call agenda

    Every panel disaster I’ve produced traces back to a skipped or lazy prep call. Thirty minutes, all panelists on the line, camera on, run it like a meeting with an agenda — because it is one. Here’s the exact split I use:

    MinutesAgenda itemWhat you’re actually doing
    0–5Tech and rolesConfirm platform, audio, who admits from the lobby, who watches chat
    5–15Theme walk-throughShare the 3 themes and opening questions — not the follow-ups
    15–20The 90-second contractGet verbal agreement on answer length and your cut-in phrase
    20–25Disagreement mappingAsk “where do you two see this differently?” and write down the answers
    25–30Closing assignmentsAssign the one-sentence takeaway each panelist will deliver, and the order

    Disagreement mapping is the step people skip and the one that matters most. Panelists default to violent agreement on camera — it feels polite and it plays dead. If you know going in that your two guests split on, say, gating content, you can tee that up live and get the only kind of moment audiences remember from panels. Pair this call with a written brief so nobody arrives cold; our guest speaker briefing template covers what to send and when.

    Build a question bank, not a script

    A scripted panel sounds scripted. A winging-it panel sounds lost. The middle path is a question bank organized by theme. For a 45-minute panel — still the sweet spot in our programs — I build three themes, and each theme gets the same four-question structure:

    • One open question. Broad enough that any panelist can take it first. “What’s changed about pipeline reviews in the last two years?”
    • One specific question. Aimed at a named panelist, grounded in their experience. “Maria, you run this with a six-person team — what breaks first at that size?”
    • Two follow-ups. Written in advance but deployed based on what was actually said. “You said ‘eventually’ — what’s the real timeline?” and a devil’s-advocate version of the theme.

    Twelve questions total. You will not ask all twelve — the follow-ups exist so you’re never staring at a doc while a panelist finishes, deciding what’s next. Send panelists the themes and the open questions ahead of time. Keep the follow-ups to yourself. Rehearsed answers to open questions are fine; rehearsed answers to follow-ups kill the room.

    Time-box answers to 90 seconds

    The math is unforgiving. Three panelists, one answer each per question, at three minutes an answer, means one question burns nine minutes — you’d get five questions into a 45-minute session. At 90 seconds an answer you roughly double your question count and the pace stops sagging.

    The trick is that 90 seconds is a contract, not an ambush. In the prep call I say it straight: “Answers are 90 seconds. Sixty is better. If you’re still going at two minutes I’ll jump in, and it won’t be rude — we agreed to it here.” Panelists are almost always relieved. Nobody wants to be the one who talked too long; they just have no sense of time once they’re rolling. I also tell them my cut-in phrase in advance, so when it happens live it registers as choreography, not correction.

    Cutting off ramblers politely

    Even with the contract, someone will run long. Interrupting feels confrontational, so weak moderators wait — and the room pays. Three moves that work, in escalating order:

    • Name-and-redirect. Use their last phrase as a handoff: “‘Tooling debt’ — Sam, I want your take on exactly that.” The rambler hears their words repeated back, which reads as respect, not a hook off stage.
    • Summarize-and-pivot. “So the short version is: start smaller than you think. Let’s push on that —” You’ve given their answer an ending they weren’t finding themselves.
    • The direct hold. “I’m going to pause you there because we have to get to Q&A — hold the rest of that thought, I’ll come back if we have time.” Use it once, at most. It works precisely because you set the 90-second contract earlier.

    What never works is hoping. A moderator who won’t interrupt has resigned from the job in front of everyone.

    Filtering audience Q&A live

    Never read audience questions verbatim, and never take them in arrival order. Have a producer — or you, during panelist answers — triage every incoming question into three buckets: ask now, save for later, skip. Then rewrite before you read. A four-sentence chat message becomes “We’ve had a few questions about pricing under $10k deals — who wants it?” You’re not misquoting anyone; you’re doing the asker the favor of making their question land.

    Two more rules from the trenches: seed the first Q&A question yourself, because the first hand up is always the slowest, and cap Q&A at the number of strong questions you actually have — eight minutes of great Q&A beats fifteen minutes of filler. If your registrations skew quiet, the fix is upstream: our webinar engagement tactics playbook covers how to warm a chat up long before the Q&A block.

    Never end on a trailing question

    The most common panel ending in B2B: moderator glances at the clock mid-answer, panelist trails off, moderator says “well, looks like we’re out of time, thanks everyone.” The final impression of the event is an apology. Attendance data makes this worse — your replay audience, which in our programs often matches or exceeds the live number, will scrub to the end looking for conclusions and find none.

    Close the way you planned in minute 25 of the prep call. With five minutes left, stop taking questions — announced, not sheepish: “Last question folks, because I promised you takeaways.” Then each panelist delivers the one-sentence takeaway they were assigned, in the order they were assigned. One sentence, enforced with a smile. You go last, name the next step once — the replay, the follow-up email, the resource — and end thirty seconds early rather than one second late. What happens after that close matters as much as the close itself; that’s the webinar follow-up playbook.

    Frequently asked questions

    How do you start a webinar panel discussion?

    Skip round-robin introductions. Introduce each panelist yourself in one sentence — name, role, and the one credential that matters for this topic — then ask your first open question inside the first two minutes. Ten-second intros from a prepared moderator beat two-minute autobiographies every time.

    How many panelists should a webinar panel have?

    Three is the ceiling for a 45-minute session, and two often outperforms it. Four panelists at 90 seconds per answer means each question costs six minutes before you’ve said a word — the format collapses into serial monologues.

    Should panelists see the questions in advance?

    Send the themes and the open questions, hold back the follow-ups. Panelists prepare better answers when they know the terrain, but pre-baked answers to every question produce a table read, not a conversation.

    How do you politely cut off a panelist who talks too long?

    Set a 90-second answer agreement in the prep call so interruptions are pre-authorized, then cut in by repeating the panelist’s own last phrase and handing it to someone else — “‘hidden cost’ — Priya, does that match what you see?” It reads as engagement, not a hook.

    What makes a good panel moderator?

    Preparation and the willingness to interrupt. The best moderators I’ve produced talk for less than 15% of the runtime, but every minute of the other 85% happens inside a structure they built — themes, time-boxes, mapped disagreements, and a rehearsed close.

    Moderation is lesson-one material from our courses — see what’s coming, or get the free lessons by email as they ship.

  • How to Brief a Guest Speaker So They Don’t Wing It

    How to Brief a Guest Speaker So They Don’t Wing It

    The guest speaker joined our green room nine minutes before a 2,000-registrant webinar and asked what the topic was. Not a joke — a VP at a Fortune 500 software company, booked six weeks earlier by his own marketing team. The moderator carried him through it, but the Q&A was thin, the demo never happened, and the replay was too rough to promote. That webinar didn’t fail on stage. It failed on booking day, when nobody briefed him.

    After producing more than a thousand B2B webinars, I can tell you webinar speaker preparation is not a rehearsal problem — it’s a cadence problem. Guests wing it because the information arrives late, scattered across four email threads, or never at all. This playbook is the exact two-touch system we use: a briefing packet the day the speaker is booked, and one platform rehearsal at least 24 hours before the event. The briefing email below is copy-paste ready.

    Why smart speakers still wing it

    It’s almost never arrogance. The speakers who show up cold are usually the busiest and most senior — they said yes in a hallway conversation, their calendar swallowed the details, and the only thing they retained is the date. Then the production team makes it worse by drip-feeding logistics: slides deadline in one email, join link in another, format change in a Slack message they never saw.

    The fix is structural, not motivational. If everything a speaker needs lives in one email they received the day they were booked, “I didn’t know” stops being possible. In our programs, the sessions with a briefed and rehearsed guest consistently hold more of the room to the end — and since live attendance already only lands between 35–50% of registrations, you can’t afford to leak the people who actually showed up.

    The two-touch cadence

    Everything in this playbook hangs on two touches. Not five check-ins, not a shared doc nobody opens — two.

    • Touch one — booking day. The briefing packet goes out within hours of the speaker saying yes, while the commitment is still warm. It contains every date, deadline, and expectation in a single email. Send it three weeks later and you’ve already lost them.
    • Touch two — the rehearsal, 24+ hours out. Thirty minutes, on the actual webinar platform, with the actual moderator. Never day-of: if the rehearsal surfaces a broken mic or a missing slide deck, you need a night to fix it, not eleven minutes.

    Between the two touches, the speaker gets exactly one other message from you: the slides-due reminder. Every additional email trains them to skim you. Meanwhile your reminder sequence works on the audience — those two tracks should never share a thread.

    What goes in the briefing packet

    The packet is one email plus two attachments — the slide template and the run of show. If it takes the speaker more than five minutes to read, it’s too long. Cover these seven items, always in the same order:

    • The promise. Two sentences on what the audience was told they’d get. Speakers drift when they don’t know what was sold.
    • The audience. Who registers, their seniority, what they already know. A room of practitioners and a room of VPs need different talks.
    • The format and clock. Total runtime, their segment length, Q&A allocation. We hold to 45 minutes total — the sweet spot across our programs.
    • Slides deadline. Five business days out, template attached. Enough time for one honest revision pass.
    • Rehearsal date and length. Named in the packet, calendar invite sent the same day.
    • Tech expectations. The audio and camera standards below, stated up front so nobody is surprised at rehearsal.
    • The run of show. Attach your run-of-show template with their segments highlighted. Speakers behave differently when they can see the whole machine.

    The exact speaker briefing email

    This is the template we send, lightly genericized. Steal it.

    Subject: [Webinar title] — everything you need in one email

    Hi [Name] — great to have you on [title] on [date] at [time] ET. Everything you need is below, so there are no other threads to dig through.

    • What we promised the audience: [two sentences, plus the three questions registrants expect answered]
    • Format: 45 minutes total — [X] minutes of your material, [X] of moderated discussion, 10 of live Q&A. [Moderator] keeps time so you don’t have to.
    • Audience: [who they are, seniority, what they already know]
    • Slides: due [date — 5 business days out]. Template attached, or send yours and we’ll adapt it.
    • Rehearsal: [date/time], 30 minutes on the actual platform. Calendar invite lands right after this email.
    • Tech: wired headset or external mic, camera at eye level, hard-wired internet if you can get it. We check all of this at rehearsal.
    • Day of: your presenter link is different from the attendee link — it’s in the calendar invite. Please join 20 minutes early.

    If anything on this list doesn’t work, reply and we’ll fix it. Otherwise you’ll get exactly one more email from me — the slides reminder — and then I’ll see you at rehearsal.

    The 30-minute rehearsal agenda

    A rehearsal is not a full run-through — asking a senior guest to perform their talk twice is how you get a no. Thirty minutes, on the real platform, structured like this:

    • Minutes 0–5: tech check. Mic, camera, lighting, screen share, notifications off. Fix problems now, not day-of.
    • Minutes 5–10: platform walkthrough. Where the Q&A panel lives, how the moderator hands off, what happens if they drop and rejoin.
    • Minutes 10–20: content spot-check. Their opening two minutes out loud, each transition, and one hard audience question answered live. The opening is where nerves live; transitions are where trainwrecks live.
    • Minutes 20–25: run of show. Walk the timeline minute by minute so they know what happens before and after their segment.
    • Minutes 25–30: contingencies. Join time, a backup phone number for audio, and exactly who to message if something breaks mid-session.

    Audio and camera standards

    Audiences forgive average slides. They do not forgive bad audio — it’s the top complaint in our post-event surveys, ahead of content, length, and everything else. Our minimum standards, stated in the packet and verified at rehearsal:

    • Microphone. Any wired headset or USB mic. The laptop’s built-in mic plus its own fan noise is the single most common quality killer we see.
    • Camera. At eye level — stack books under the laptop if needed. Main light source in front of the face, never a window behind.
    • Connection. Wired ethernet where possible. If it has to be wifi, same room as the router and nobody else in the house on video calls.
    • Environment. Door closed, phone on do-not-disturb, calendar blocked 30 minutes past the end time so no meeting hard-stops your Q&A.

    The exec who refuses to rehearse

    You will meet this person. Senior, in demand, and their EA tells you a rehearsal “won’t be possible.” Escalating rarely works. What works, in the order we try it:

    • Shrink the ask. Offer a 15-minute tech check instead of the full 30. Most refusals are calendar objections, not principle.
    • Reframe who it protects. The honest line: “The rehearsal isn’t for us — it’s so you’re never surprised on camera in front of 800 people.” That lands with executives.
    • Change the format. If they truly won’t prepare, stop expecting a presentation. Switch to a moderated interview — get their talking points from the EA, build the questions yourself, and let a strong moderator do the structural work. It’s the same reason panels often beat solo sessions with unpredictable guests, and why moderation skill is the real insurance policy.
    • Hold one hard line. A 10-minute green-room check on the day, 20 minutes before doors open, is non-negotiable. In twenty years I’ve never had a speaker refuse that once the rehearsal fight was already conceded.

    Frequently asked questions

    How do you prepare a guest speaker for a webinar?

    Use a two-touch cadence: send a single briefing email on booking day covering the audience, format, deadlines, and tech standards, then run a 30-minute rehearsal on the actual platform at least 24 hours before the event. Everything else — nagging, shared docs, check-in calls — adds noise without adding preparation.

    What should be included in a speaker briefing document?

    Seven things: the promise made to the audience, who the audience is, the format and time allocations, the slides deadline, the rehearsal date, minimum audio/camera standards, and the run of show with the speaker’s segments highlighted. One email, two attachments, readable in five minutes.

    How far in advance should you brief a webinar speaker?

    The same day they’re booked — while the yes is still warm. Slides come due five business days before the event, and the platform rehearsal happens 24 hours or more ahead, never on the day itself. Day-of rehearsals leave no time to fix whatever they uncover.

    Do webinar speakers really need to rehearse?

    Yes, but not the way most teams mean it. A full run-through is unnecessary and senior guests will refuse it. What matters is 30 minutes on the real platform: tech check, handoff practice, the opening two minutes out loud, and one hard question answered live. That covers the moments where webinars actually break.

    This is lesson-one material from our courses — see what’s coming, or get the free lessons by email as they ship.

  • The Webinar Run of Show Template I Use for Every B2B Event

    The Webinar Run of Show Template I Use for Every B2B Event

    Nine minutes before go-live on a 700-registrant product webinar, our keynote speaker’s laptop decided it was the perfect moment to install updates. Nobody panicked — because line 14 of the run of show said exactly who would cover, which backup deck they’d share from, and which producer would text the speaker a rejoin link. We started on time. Maybe five people in the audience ever suspected anything.

    That document is the difference between a webinar that feels produced and one that feels improvised. Below is the webinar run of show template I’ve refined across a thousand-plus enterprise B2B webinars — the minute-by-minute rundown, the pre-show call agenda, the cue language, and the failure plans. Copy it, adapt it, and stop running live events from memory.

    What a run of show is — and what it isn’t

    A run of show is not an agenda. An agenda is what the audience sees: three bullet points on a title slide. A run of show is the backstage document — a minute-by-minute rundown that assigns every action to a named person with an exact timestamp. Who launches poll two, and at what minute. Who is watching the Q&A pane. What the moderator says, word for word, if the demo environment dies.

    Mine is a single shared spreadsheet. One tab, frozen header row, sorted by time. Everyone on the crew has it open in a second monitor for the entire event. If a decision has to be made live, the answer should already be written down. The document thinks so the humans don’t have to.

    The production schedule that feeds it

    The run of show is the last artifact in a chain, not the first. Working backward from event day, here’s the webinar production schedule that makes the document trustworthy instead of aspirational:

    • T-minus 3–4 weeks. Topic locked, registration page live, promotion running. Your reminder emails should already be drafted — the four-email reminder sequence is its own playbook.
    • T-minus 1 week. Speaker briefing call. Slides at 90%, polls written, run of show drafted and shared. My guest speaker briefing doc covers what to send them.
    • T-minus 2–3 days. Full tech check and dry run — real platform, real slides, real handoffs. I run it off the tech check and dry run checklist, and every issue found gets written into the run of show as a cue or a contingency.
    • T-minus 1 day. Final version locked. No edits after this point except timestamps. A run of show that changes on event morning is worse than none, because half the crew is working from the old one.

    The minute-by-minute template

    Here is the actual rundown structure for a standard 45-minute B2B webinar with one host, one speaker, and one producer. Times are relative to go-live. Adapt the segment lengths, keep the columns.

    TimeSegmentOwnerCues and notes
    T-30Pre-show callProducerAll crew on the platform. Audio, video, slides, screen share each tested live. Backup phone numbers confirmed.
    T-10Waiting room opensProducerHolding slide up, music on if the platform supports it. Speaker goes quiet — no last-minute slide edits.
    T-5Final go/no-goProducerVerbal confirmation from host and speaker. Recording armed. Q&A and chat panes staffed.
    0:00Cold openHostScripted first 90 seconds — see below. Recording starts on the first word, not after housekeeping.
    0:02Housekeeping + poll 1HostOne sentence on Q&A logistics. Producer launches poll 1 on the phrase “let’s see who’s in the room.”
    0:05Speaker handoffHost → SpeakerHost asks the setup question, speaker answers into the content. No “over to you” dead air.
    0:18Poll 2 + results riffProducer / SpeakerLaunch cue: “curious what this looks like for you.” Speaker reacts to results for 60–90 seconds.
    0:20Q&A checkpointHostHost voices one strong question from the pane mid-stream. Signals the audience the pane is alive.
    0:35Wrap of contentSpeakerHard stop. Anything uncovered moves to follow-up. Producer posts resource link in chat.
    0:36Live Q&AHostHost reads triaged questions — lanes below. Producer queues the next two in a side channel.
    0:44CTA + closeHostOne call to action, stated twice. End on time. The replay email is part of the follow-up playbook.

    Two rules make this table work. First, every row has exactly one owner — shared ownership is how polls launch twice or never. Second, cues are spoken phrases, not clock times. A producer listening for “let’s see who’s in the room” fires the poll at the right moment even when the show is running two minutes long, which it always is.

    The T-30 pre-show call

    Thirty minutes before go-live, everyone joins the actual event platform — not a separate call. This matters. Testing audio on Zoom and then presenting on a different platform tells you nothing. The pre-show agenda takes twelve minutes when nothing is wrong, which leaves eighteen for when something is.

    • Audio and video, per person. Each presenter speaks for twenty seconds while the producer listens for levels, echo, and fan noise.
    • Screen share, live. The speaker shares the real deck and advances three slides. Animations and embedded video are where shares die.
    • Polls staged. Producer confirms every poll is loaded and in order. Misordered polls are the most common production error I see.
    • Backchannel test. Crew confirms the side channel — a group text or Slack thread — with a test message. This is where “your mic is muted” lives during the show.

    The first five minutes: cold open

    Most webinars burn their highest-attention minutes on logo slides and “we’ll wait a few minutes for people to join.” Don’t wait. Across our programs, live attendance typically lands between 35–50% of registrations, and the people who showed up on time are your most engaged segment — rewarding them with dead air is backwards.

    The cold open is 90 scripted seconds: a sharp claim or a number that earns the next 45 minutes, the speaker’s one-line credential, and the single promise of the session. Then two sentences of housekeeping, poll one, and handoff by minute five. Write those 90 seconds out word for word in the run of show. It’s the only part of the event I fully script, and it’s the part that most changes how the whole show feels.

    Cue language: polls, Q&A lanes, handoffs

    Q&A triage is the piece most run of show templates skip. During the event, the producer sorts every incoming question into one of three lanes, marked directly in the Q&A pane or the backchannel:

    • Lane 1 — ask live. Broadly relevant, answerable in under two minutes. These get queued for the host, best question first — never “in the order received.”
    • Lane 2 — answer in text. Narrow, technical, or account-specific. The producer or a subject-matter teammate answers in the pane during the show.
    • Lane 3 — follow up after. Pricing, competitive, or anything deserving a real conversation. Logged with the asker’s name and routed to sales or the speaker post-event.

    The host never reads the raw pane. They read the producer’s queue. That single change is most of what separates a smooth Q&A block from a rambling one — I go deeper on this in how to moderate a webinar panel, where triage gets harder with every added speaker.

    When things break: backup plans

    The last section of my template is a short table of failure modes with a named response. Not “we’ll figure it out” — a name and an action. Speaker drops: host bridges with the two backup discussion questions written in the doc while the producer texts the rejoin link. Slides freeze: producer shares the mirror copy of the deck from their own machine within 30 seconds. Platform-wide outage: producer emails registrants the backup link within five minutes, from a template drafted before the event.

    You will use these rarely. In our programs, maybe one event in fifteen touches a contingency row. But the crew that knows the plan exists runs calmer for all fifteen — and calm is audible on a live stream.

    Frequently asked questions

    What is a run of show for a webinar?

    A run of show is the internal minute-by-minute production document for a live event. It lists every segment with a timestamp, a single named owner, spoken cues for actions like poll launches, and contingency plans. The audience never sees it — it exists so the crew never has to improvise a decision live.

    What is the difference between a run of show and an agenda?

    An agenda is audience-facing and lists topics. A run of show is crew-facing and lists actions: who does what, at which minute, triggered by which cue. A 45-minute webinar might have a three-line agenda and a 25-row run of show.

    How detailed should a webinar run of show be?

    Detailed enough that a competent stand-in could run the event from the document alone. In practice that’s 20–30 rows for a single-speaker webinar: every segment, every poll, every handoff, and every failure plan. If a row has two owners or no cue, it isn’t finished.

    Who should own the run of show?

    The producer — the person not on camera. Hosts and speakers contribute, but the producer builds it, locks it the day before, and calls the show from it. On small teams where one person hosts and produces, the document matters even more, because it’s the only “second brain” in the room.

    Does this template work for virtual events other than webinars?

    Yes — the structure holds for panels, virtual summits, and hybrid sessions. Multiply the pre-show call length by the number of presenters, add a row per handoff, and keep the three-lane Q&A triage exactly as is. The columns don’t change; the row count does.

    Want the fill-in-the-blank version of this template? It’s lesson-one material from our courses — see what’s coming, or get the free lessons by email as they ship.