Why the microphone is the problem
A microphone in the aisle selects for confidence, not for the question the room most wants answered. The people who ask are the people who are comfortable standing up in front of four hundred colleagues; the junior analyst with the sharpest question, the guest who is not speaking their first language and the person who does not want their manager to see them ask all stay quiet. Then there is the logistics: a runner, a wait while the microphone travels, a question nobody else can hear.
Written questions from phones change who speaks. Everyone can ask at the moment the question occurs to them, not when the host finally opens the floor, and the host gets to see the whole set before choosing what to take. The cost is that somebody now has to read them — which turns out to be the most valuable part.
No app, one code
Every step between "I have a question" and "it has been sent" loses people. An app to download loses most of them: the venue Wi-Fi is slow, the store wants a password, and the session is over before the install finishes. A web page opened from a QR code loses almost nobody, because a phone camera already knows how to open it.
Put the code where eyes already are: on the slide that introduces the session, on the table cards, on the screen beside the stage while people are taking their seats. Make the code open the questions page directly, not a home page with a menu. If guests already have a personal page for the event from their invitation, put the same questions there, so the people on your list do not need to scan anything at all.
Moderate before the room sees anything
An unmoderated question wall is a stage you have handed to the least considerate person in the room. The rule that makes live Q&A safe is simple: nothing reaches the screen or the room’s list until a person on the team has approved it. The moderator rejects what is abusive or off-topic, hides what is a duplicate, and lets everything else through quickly — a queue that sits unread for ten minutes is its own kind of failure.
Give the moderator a laptop or tablet, a seat with a view of the stage, and a clear brief: what the host wants to cover, what is out of bounds, and who to signal if a question needs a decision. On a panel, the moderator is often the person who keeps the session alive; treat it as a role, not a favour somebody does from the back row.
Let the room vote
Once a question is approved, let everyone see it and vote for it. Upvotes do two things: they tell the host which questions the room actually cares about, and they collapse ten versions of the same question into one with a large number beside it. Show the approved questions ordered by votes, and let each phone vote for a question once — otherwise the result measures enthusiasm for tapping rather than interest.
Decide in advance whether askers may add their name. Named questions feel more accountable and suit internal events where people know each other; anonymous ones bring out the questions people would never sign. Many organisers allow both and let the asker choose.
On the stage: one question at a time
The host should read the question aloud before the speaker answers — the room cannot hear a phone. Mark the question being answered so that the room and the screen both show it, and mark it answered when it is done, so that nobody asks it again. If a question is answered by an earlier answer, say so and move on; the asker will see that it was taken.
Keep the screen simple during Q&A: the question on stage, the next two or three by votes, and the code to join for anyone who arrived late. Do not put the moderation queue on the public screen, ever.
Tell the askers what happened
The quiet failure of written Q&A is the question that disappears. The asker never learns whether it was read, rejected or simply not reached. A good system tells them: waiting, shown to the room, answered, or not shown. "Not shown" is not an insult — sessions run out of time — but silence feels like one.
If questions remain when time is up, decide on the spot what happens to them and say it from the stage: answered in a follow-up email, passed to the speaker, or left where they are. Then do what you said.
Keep it fair and keep it standing
A live channel in a full room will be tested. Limit how many questions one phone can send in a few minutes, and how fast one network can send them, so that nobody can flood the queue. Recognise each phone without asking for a name or an account — a signed key for this event is enough — so that "one vote per phone" means something. And make sure the questions page survives a venue connection that comes and goes: it should keep what it last loaded, say how old it is, and reconnect by itself.
- One QR code on the slide, the table cards and the screen; it opens the questions page directly.
- No app, no account; guests on the list find the same page from their invitation.
- A named moderator; nothing reaches the room until approved.
- Approved questions visible to all, ordered by votes, one vote per phone.
- Names optional, decided in advance.
- The question on stage marked; answered ones marked answered.
- Askers told whether their question was shown, answered or not shown.
- Rate limits per phone and per network; a page that survives the venue Wi-Fi.