How to say "I don't know" in a meeting and still sound competent

Someone senior asks you a direct question. It's a fair question. You don't have the answer, and you can feel that you don't have it, and now there are two problems: the answer, and the two seconds of silence in which everyone can hear you not having it.

If English is your second language, those two seconds are worse. You're not only searching for the fact. You're also searching for a way to say "I don't have the fact" that doesn't sound like I'm not good enough to be here. Most people solve this badly: they either say "I don't know" flat, and sound lost, or they start talking around the question, and sound evasive. Both are worse than the silence.

Here's the thing to hold on to: nobody in the room expects you to know everything. What they expect is to learn, within one sentence, what you do know and what happens next. "I don't know" fails not because it's honest but because it's incomplete.

What it sounds like when it's done well

Three real moments from our meetings. In each one someone is asked something they can't fully answer, and none of them says "I don't know."

1. Answer the shape, then the gap. In an escalation meeting, the sponsor asks the technical lead, Priya, where a critical deliverable really stands. Priya's answer:

"It's on track. But 'on track' assumes I'm building it, not firefighting. Two days a quarter is the difference between comfortable and tight."

Look at the order. First, the thing she knows: on track. Then, immediately, the condition that makes that answer uncertain. She has converted "I'm not sure" into "here is what my certainty depends on." The sponsor now knows more than if Priya had said "I think it's fine." That's the standard: your not-knowing should add information.

2. Give the number you have, then name what the number misses. Same meeting, earlier. The sponsor cuts through: "Give me a number, not an adjective." Priya has a number, but it's rough:

"Four breaks, four reruns. Around six hours of my time, plus half a day of Marco's. So — call it two days a quarter, and growing."

"Call it" is doing a lot of work. It says: this is an estimate, I'm labelling it as one, and I'm giving it to you anyway. Native speakers use "call it", "roughly", "ballpark" to mark uncertainty without apologising for it. Compare with "I'm not 100% sure but maybe around..." which marks the same uncertainty and also marks you as nervous.

3. Say where the answer lives, and go get it. In a trade negotiation, the buyer asks for ninety-day payment terms and adds a small test: "You can decide that here, surely — or do you need permission?" It's designed to make the supplier, Edmund, either overreach or look junior. Edmund:

"Structural terms sit outside what I settle in this room — you know that. So yes: I'm going to step out, make one call, and come back with an answer you can rely on instead of one I'd have to unwind on Thursday. Ten minutes."

He doesn't know the answer and he says so. But he says it as a process: here's why I can't answer, here's what I'll do, here's when. The buyer's response is not contempt. It's "ten minutes, the coffee will survive." A clear "I'll find out" from someone who obviously knows where to find out reads as competence, not weakness.

The pattern

All three do the same thing in a different order: known + unknown + next. What I know, what I don't, and what happens about the part I don't.

• "It's on track, assuming X. Here's what X depends on."
• "Call it two days. The exact figure I'd have to check."
• "That sits outside what I can settle here. I'll make one call and come back in ten."

You need two or three of these, in English, in your mouth, before the meeting. Not a list of twenty phrases. Two or three that you've actually said out loud enough times that they come out before the panic does.

The one thing to stop doing

Stop starting with "sorry." Sorry, I'm not sure. Sorry, I don't have that. You're not apologising for a mistake; you're reporting a fact about the state of your knowledge. "Sorry" turns a neutral fact into a small failure, and it costs you the first second, which is the second you needed for "call it."

Say the thing you know first. Then the gap. Then the next step. Nobody remembers that you didn't know. They remember that you were clear about it.

Practice it on Sarah. Listen to the escalation meeting and stop at "give me a number, not an adjective." Answer her before Priya does, out loud. Then hear how Priya handles it.