Questions to Ask Speakers
Twenty questions for the audience side of a talk, panel, or lecture. Each one is written to be said out loud, into a microphone or in the hallway afterward: short enough not to hold up the room, and aimed at what the speaker knows but did not have time to cover.
The questions
Open any question for the note
If people forget everything else, what's the one thing you hope they remember?
Why ask it
Speakers have usually rehearsed this answer, so the useful part is comparing it against what the talk actually spent its minutes on. When the headline and the minutes disagree, the minutes are the honest version.
What did you have to cut from this talk for time?
Why ask it
The cuts are normally the caveats, the failure cases, and the material that was hardest to defend, which is exactly what an audience needs. It is also an easy question to answer generously, which makes it a good first one from the floor.
Which of your slides do you get the most pushback on?
Why ask it
Naming the contested claim shows where the field is genuinely unsettled rather than where the speaker sounds confident. Anyone who says nobody pushes back has either a very safe talk or no experience of a hostile room.
How does this hold up if you don't have the budget or the headcount you had?
Why ask it
Most talks describe what worked at a scale the audience cannot match. Naming your constraint makes the speaker separate the parts of the approach that are load-bearing from the parts that were luxuries.
What did you believe about this five years ago that you don't believe now?
Why ask it
You find out whether their thinking has moved or whether this is the same talk they have given since then. A specific reversal with the reason attached marks someone who keeps track of their own mistakes.
What's the strongest argument against your position?
Why ask it
How accurately someone can state the opposing case shows how seriously they have engaged with it. A caricature of the other side means their confidence rests on not having looked closely.
Where has this approach failed, and did you find out why?
Why ask it
Failures arrive with conditions attached, and the conditions are what let you predict whether it will fail for you too. A speaker with no failures to report is describing a demo rather than a practice.
How long did this take before it started looking like it was working?
Why ask it
Timelines compress in the telling, and the distance between the first attempt and the presentable result is usually much longer than a talk implies. Hearing that it took two years stops you abandoning it in week three.
How would we know within a month whether this is working for us?
Why ask it
This turns an idea into something testable and forces the speaker to name a signal rather than a benefit. If they cannot describe an early indicator, the approach may only be judgeable in hindsight, which you want to know before committing.
What did you expect to be hard here that turned out to be easy?
Why ask it
The answer usually points at a step everyone over-prepares for, which saves you effort immediately. It also draws a more candid reply than asking what was difficult, because admitting it costs the speaker nothing.
Who disagrees with you on this that you still respect, and what do they say?
Why ask it
This surfaces the live debate in the field and hands you a name to read next. Refusing to name any credible opponent tells you how much of the talk was argument and how much was posture.
Which part of this were you least sure about while you were writing it?
Why ask it
Speakers know where the thin spots in their own material are, and most will say so if you ask plainly and without hostility. It marks the claims worth checking before you repeat them to your own team.
What's a question you wish audiences would ask you and never do?
Why ask it
Rooms tend to ask the same three questions, so this hands the speaker the material they came prepared to share and never reached. It reliably produces the longest answer in the session.
If you were starting this on Monday with no budget, what's the first thing you'd do?
Why ask it
You get a concrete first move instead of a principle. Vagueness here suggests the approach quietly depended on money, authority, or an existing team that never made it into the slides.
What does this cost, in time or money, before it starts paying off?
Why ask it
Talks describe the outcome and skip the trough in between. Knowing the depth and length of that dip tells you whether you could survive it, and whether it is worth pitching internally at all.
Which of your recommendations should most people skip?
Why ask it
Giving a speaker permission to rank their own advice down often produces the single most useful sentence of the Q&A. Someone who insists every part is required has not watched many other people try it.
What's a question you get asked constantly that you think is the wrong question?
Why ask it
This reframes the problem, and people who work in a field daily tend to have a sharp answer ready. It also tells you which assumption most of the room is walking in with.
What have you read or watched recently that changed how you think about this?
Why ask it
Asking what changed their mind rather than for a reading list gets you the one or two sources that actually mattered. Notice whether anything they name comes from outside their own specialty.
Is there data you wish existed here that doesn't?
Why ask it
You learn the limits of the evidence behind the talk from the person best placed to know them. It is also the courteous way to ask how much of the argument rests on experience rather than measurement.
If someone tries this and gets stuck, is there a good way to reach you?
Why ask it
This closes with something actionable and lets the speaker set their own terms, whether that is an email address, a newsletter, or nothing at all. Asked from the floor it is easier than intercepting them at the coffee table, and the answer is usually more generous in public.
Asking well in a Q&A
Practical guidance for the conversation itself
Before your turn at the microphone
- Write the question down during the talk and cut it to one sentence. Questions composed while standing in the aisle come out as three questions joined by "and also."
- Check whether the speaker already answered it on a slide you half-read. Being told "I covered that" costs you the room's attention.
- Decide which single answer you want. If you want a recommendation, ask for a recommendation; if you want a story, ask what happened.
- Find out how questions are handled. Some events take a roving microphone, some collect cards, some run everything through a moderator who will merge yours with someone else's.
- If the session is remote, get your question into the chat early. Moderators usually work top to bottom and run out of time long before the queue does.
Phrasing that gets a real answer
- Skip the preamble. Your job title and your admiration for the talk can wait; the room starts losing patience at about fifteen seconds.
- Ask for a specific case rather than a general view: what happened the first time, what the number was, who objected.
- Give the speaker an exit. "If that's not something you can talk about, say so" makes it easier for them to answer the parts they can.
- Avoid stacking. "And a follow-up" usually means only the second half gets answered, and it is normally the weaker half.
- Do not use the microphone to make a point. If your question ends with the audience unsure whether you asked anything, you have given a short talk of your own.
Catching them afterward
The hallway is where the caveats live. Speakers are more candid when they are not on record and not on a clock, so save anything about failures, internal politics, or what they would not put on a slide for the moment after the session ends. Lead with the specific: name one thing they said and ask what happened next. Keep it to two or three minutes unless they extend it, because there is usually a queue behind you and a schedule ahead of them. If you want anything ongoing, ask for one small, defined thing rather than "to pick your brain."
Adapting to the format
Panels
Direct the question at one named person, otherwise the first panellist answers at length and the rest agree. If you want disagreement, ask the same question of two people who clearly differ.
Academic seminars
Method questions are normal and expected here in a way they are not at a commercial conference. Ask about sample, controls, and what result would have falsified the claim.
Keynotes with no Q&A
Assume you get one shot in a corridor or a signing line. Have a single sentence ready and lead with the question rather than the compliment.
Internal talks at your own company
Everything you ask is heard by colleagues as well as the speaker. If your real question is critical, ask the version that is answerable in public and take the rest offline.
What tends to go wrong
- Asking something a search would answer in ten seconds. Spend the question on what only this person could tell you.
- Turning the Q&A into a private consultation about your own situation. Ask the version other people also need answered, then take the detail offline.
- Testing the speaker. Trying to catch them out gets a defensive answer and teaches the rest of the room nothing.
- Asking for predictions about five years out. The answers are entertaining, unverifiable, and forgotten by the time you leave.
- Accepting a non-answer out of politeness. One follow-up sentence, "Sorry, I meant specifically the first month," is fair and usually welcome.