What to Do When You Don't Know the Answer | Elevated You

You're mid-presentation. A stakeholder asks a question you can't answer. Your mind goes blank.

What do you do?

For a lot of technical professionals, this is one of the most dreaded moments in any customer or stakeholder meeting. And the way most people handle it - bluffing, waffling, or getting defensive - actually does far more damage than simply not knowing the answer.

Here's what actually works. And why honesty, handled well, is one of the most powerful tools in your technical storytelling toolkit.

Why This Moment Feels So Threatening

Technical professionals are experts. That identity matters. When someone asks a question you can't answer, it can feel like a direct challenge to your credibility - especially in front of customers, senior stakeholders, or leadership.

When I was representing Microsoft, some people in the audience would actively try to catch me out. Ask the question the Microsoft guy couldn't answer. Prove they knew more. It's a game some people play in high-stakes technical environments.

Early on, I'd try to bluff my way through. Spin something that sounded plausible. Keep talking and hope no one noticed the gap.

It never worked. Experienced audiences can smell a bluff immediately. And the moment they catch it, you've lost far more than the answer to one question. You've lost their trust.

The Three Things That Kill Your Credibility

Before we get to what works, it's worth naming what doesn't. These are the three most common responses technical professionals fall back on - and all three make the situation worse.

Bluffing. Making something up, or dressing up uncertainty as confidence. The risk is obvious. If the person asking already knows the answer - and often they do - you've just demonstrated that you'll mislead people under pressure. That's a trust-destroying moment that's very hard to recover from.

Waffling. Talking at length without actually saying anything. This is the more common version. You fill the air with words, use a lot of "well, it depends" and "there are various factors", and eventually trail off. Your audience learns nothing. Worse, they've now watched you lose control of the room.

Getting defensive. Taking the question as a personal challenge and responding with body language or tone that signals discomfort or irritation. Even if you're not consciously aware of doing it, audiences pick this up immediately. Defensiveness reads as insecurity. It suggests you're not confident enough in your material to handle scrutiny.

What Actually Works: Two Simple Responses

After years of presenting to customers, stakeholders, and conference audiences, I use two approaches. Both are simple. Both build rather than damage credibility.

If you know the answer, answer it. Directly. Confidently. Without padding. A lot of technical professionals over-qualify their answers even when they're sure. Resist the urge. If you know it, say it cleanly and move on.

If you don't know the answer, say this:

"Great question. I haven't thought about it that way before. Let me think about it properly and come back to you."

That's it.

No waffle. No bluff. No performance of confidence you don't have.

And here's what surprises most people the first time they try it. The room doesn't fall apart. The audience doesn't lose faith in you. In most cases, they respect you more. Because you've just demonstrated intellectual honesty. You've shown them that you won't mislead people to protect yourself.

In a world where stakeholders are used to being dazzled by people who always have an answer, "I don't know but I'll find out" is genuinely refreshing.

The Follow-Up Is Non-Negotiable

There is one condition that makes this approach work. You have to follow through.

If you tell someone you'll come back to them with an answer, that's a commitment. Made in front of an audience. Breaking it doesn't just leave a question unanswered - it turns a moment of honesty into a moment of unreliability.

The mechanics of a good follow-up are straightforward. Note the question during the meeting - don't rely on memory. Aim to respond within 24-48 hours. Keep the follow-up focused and direct. "You asked about X. Here's my answer" is infinitely better than a long email that buries the response in preamble.

Done well, the follow-up can actually strengthen the relationship more than getting the answer right in the room would have. It shows you took the question seriously. That you did the work. That you can be trusted to do what you say.

When Someone Is Trying to Embarrass You

Not every difficult question is asked in good faith. Some people - particularly in competitive sales environments or politically charged internal meetings - ask questions designed to expose weakness rather than genuinely learn something.

The same approach still applies. "Great question. I haven't thought about it that way. Let me come back to you." You don't need to signal that you've clocked their intent. Responding with the same calm honesty you'd give to a genuine question takes the energy out of it.

What you want to avoid is rising to the bait. Getting into a battle of wits in front of an audience rarely ends well for the presenter. Even if you win the exchange, you've let one person derail the energy in the room.

Stay calm. Stay honest. Keep moving.

Why This Matters More Than People Think

For pre-sales engineers, consultants, and customer success professionals, credibility is everything. You're asking customers and stakeholders to trust your judgment, follow your recommendations, and sometimes make significant financial decisions based on your advice.

That trust isn't built by having every answer. It's built by being the kind of person who won't mislead people when they don't. By demonstrating - consistently - that you'll be straight with them even when it's uncomfortable.

"I don't know, but I'll find out" is one of the most credibility-building sentences in technical communication. Most people are too afraid to say it.

The ones who do tend to be the people audiences trust most.

A Quick Summary

• If you know it, answer it clearly and move on
• If you don't know it, say so honestly and commit to following up
• Never bluff - experienced audiences always notice
• Never waffle - it signals loss of control
• Never get defensive - it reads as insecurity
• Always follow through on the commitment you made in the room

Being honest about what you don't know isn't a weakness. In high-stakes technical environments, it's one of the strongest things you can do.

Want to build the communication and presentation skills that make you more credible in front of customers and stakeholders? Find out more about the Technical Storytelling Professional Program.