Respond to a question you cannot answer and keep the audience's trust.
Every speaker eventually gets a question they cannot answer. It does not mean you prepared badly, because no amount of preparation covers everything. What matters is how you handle the moment. Most people's instinct is to guess, and guessing is usually the worst option you have.
Picture a client asking how your product handles data stored overseas. You are fairly sure of the answer, but not completely. The room is waiting, your manager is watching, and saying "I don't know" feels like admitting you are not up to the job. So you give an answer that sounds confident. Two weeks later, the client's legal team finds the answer was wrong.
Compare the two outcomes. If a guess turns out to be correct, you gain very little, because the audience already assumed you knew. If it turns out to be wrong, the audience now has a reason to doubt everything else you said, including the parts you were sure of. And if your wrong answer led to a decision, the cost goes beyond your own credibility.
Admitting you don't know costs less than most people fear. Most audiences understand that nobody knows everything. What they want is honesty and a sense that you will get them the answer. A speaker who says they don't know but will find out often comes across as more trustworthy than one who seems to have an answer for everything, because the audience now has evidence that this speaker does not bluff.
In Singapore workplaces, saving face can push you towards a confident guess, both for your own sake and for your manager's. If you took lesson 8.2, "Hierarchy, face and hearing an indirect no", in the Communicate at work course, you have already seen how face shapes conversations at work. In a Q&A, an admission handled cleanly saves more face than a guess that unravels later.
A good "I don't know" has three parts: what you do know, what you will find out, and when you will reply.
Starting with what you know shows you are not empty-handed. You give whatever you can say with confidence, and this often answers part of the question. Saying what you will find out is honest about the gap. Giving a specific time for your reply turns that gap into a commitment.
For the data storage question, it could sound like this: "What I can tell you is that our system stores data in Singapore by default. I'm not sure what happens when a client asks for a different region, so I'll check with our engineering team and email you by Thursday."
Two vague versions are worth avoiding. "I'll get back to you on that" with no date sounds like a polite way of saying never. "That's a good question" followed by a pause sounds like stalling. Be specific about what you will find out and when you will reply.
You need these words at a stressful moment, so don't rely on improvising them. Wording you have written in advance comes out more smoothly under pressure. Arjun, who presents clinic data, prepared this line: "I don't have that figure with me. I can give you the overall pattern now, and I'll send you the clinic-level number by the end of tomorrow."
The admission only builds trust if the follow-up actually happens. Send it in writing, by the time you promised, to the person who asked. Copy anyone else who would want to know, such as the meeting organiser, or your manager if they were in the room.
Keep the message short: remind them of the question, give the answer, and offer more detail if they want it. For the data storage case, the email might read: "At Thursday's meeting you asked about data storage for clients outside Singapore. Our engineering team confirms that clients can choose to store data in other regions, and this is set up during onboarding. I'm happy to share the technical details if that would help."
A follow-up sent on time often builds more trust than a quick answer on the day would have. It shows that you listened, that you took the question seriously and that you do what you say, and people remember it.
If you cannot find the answer by the promised time, write anyway. Say what you have found so far and when you expect the rest. Missing your own deadline without saying anything undoes the trust your honest answer built in the room.
Sometimes a colleague in the room knows the answer better than you do. In that case, invite them to respond and name them: "Farah can answer this better than I can, since she ran the vendor discussions. Farah?"
Handing over is not a sign of weakness. It shows you know your team and that you care more about the audience getting the right answer than about looking like the expert on everything. It also gives your colleague credit in front of the room.
Two cautions apply. First, only hand over when you are confident the colleague knows the answer and is happy to be put on the spot. A quick word before the talk helps: in Farah's case, you would check with her beforehand whether you may pass vendor contract questions to her. Second, don't hand over too often. If every hard question goes to someone else, the audience starts wondering why you are the one presenting.
When a question you can't answer comes up, the order is the same each time. Don't guess. Say what you do know, say what you will find out, and say when you will reply, with a specific time. If a colleague in the room knows better and you agreed this beforehand, invite them to answer by name instead. After the session, send the answer in writing by the promised time, or send what you have so far and when you expect the rest.
Before your next practice session, write the exact words you will use when you do not know an answer. Include all three parts, with a real time in the last one, and read the words aloud until they come out without effort. If there is a colleague you might hand questions to, agree it with them before the talk.
Write down the exact words you will say when you do not know an answer. Use them in your next practice session.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).