Asking a good question — at a conference mic, or in the public record

Most people queue at a conference microphone having decided to ask a question and having given almost no thought to which one. The room can tell within a sentence. A good question is a small act of generosity to everyone still sitting down — it is answerable in the time given, specific enough that only someone who did the reading could have asked it, and it leaves the room smarter than it found it. That skill matters more, not less, the moment the room is a formal public meeting and your words are entering an actual public record.

The single-sentence test

Before you get in line, ask what the question is actually for. If the honest answer is “I want to know what my company should do about X,” that is a meeting request, not a floor question — take it to the speaker afterward, one to one, where a specific answer about your specific facts is actually useful. The floor is also not the place for a challenge dressed as a question, or a softball that flatters the panel without adding anything. What survives the test is narrower and better: a specific, answerable question that is generally useful to the room and ties to something actually said today — a named guidance, a stated deadline, a scenario the speaker raised themselves.

The mechanics of the floor mic

State your name and affiliation in one breath, ask the question in one or two sentences, then stop talking. The most common failure at any floor mic is a preamble that quietly eats the panel’s answer time — by the time the actual question arrives, there are ninety seconds left and the answer is rushed. Listen to what has already been asked before your turn comes; the best floor questions build on the previous answer instead of repeating a variation of it, which the panel notices and rewards with a longer, better answer.

If time runs out before you are called, do not let the question evaporate. Submit it through the event app or chat if one exists, or catch the speaker in the hallway afterward with the same one-line version you had ready — a specific question asked quietly after the session is answered more often, and more usefully, than a rushed one squeezed in before the moderator moves on.

When the record is the point

FDA public meetings, advisory committee hearings, and town halls typically run on two tracks: a spoken public-comment period during the meeting, and a formal written docket that stays open for comment, usually for some weeks afterward. The exact process — how to register to speak, the time allotted, the docket’s closing date — varies by meeting and changes without much notice, so confirm it from the agency’s own notice for that specific meeting rather than from memory of the last one you attended.

Speaking at one of these microphones is a different act than asking a conference panel a question. You are being transcribed into an official record that regulators and future readers will consult long after the room empties. Prepare a short written statement even if you plan to speak from it loosely — the discipline of writing it down sharpens the sentence, and it gives you something exact to submit to the docket afterward, in your own words, on the record.

For anything with real substance, the written comment is usually the stronger instrument, not the backup plan. It carries no ninety-second clock, it can cite a specific page or line of a pending guidance, and it can arrive under your organization’s name if that is the right call for what you are saying. A workable pattern: use the spoken slot to point sharply at the issue, and let the written comment carry the substance — that is a normal, expected division of labor, not a consolation prize for running out of time at the mic.

What actually earns a good answer

Cite what was actually said today, or in the docket, rather than the general topic — specificity is what tells the panel you did the reading. Ask for a mechanism rather than an opinion: “which section of the pending guidance would that scenario fall under” gets a materially better answer than “what do you think about this area.” And ask one question. Three questions stacked into a single turn at the mic reliably get one answered and two forgotten — pick the one that matters most and save the rest for the hallway, or the docket.

The same verification habit applies here as everywhere else on this site: comment periods, docket deadlines, and floor-question procedures are exactly the kind of detail that shifts close to the date. Check the organizer’s or agency’s own notice before you prepare your remarks, not the version you remember from last year.