How to Say "I Don't Know" Without Looking Incompetent

The Question You Can't Answer

You're in a meeting. Your boss asks you a question.

You have no idea what the answer is.

Your heart races. Everyone's looking at you.

What comes out:

"Um... well... I think maybe..."
[Fumbles through half-remembered information]
[Makes something up and hopes it's right]

What you're thinking: "If I say 'I don't know,' they'll think I'm incompetent."

The reality: Faking knowledge damages credibility far more than admitting you don't know.

But there's a right way and a wrong way to say "I don't know."

Why "I Don't Know" Feels Like Career Suicide

You Think It Makes You Look Stupid

Your fear: "They hired me to have answers. If I don't know, what good am I?"

The reality: Nobody knows everything. Pretending you do makes you look insecure and untrustworthy.

What actually looks stupid: Making up answers that are obviously wrong.

You're Worried About Being Found Out

Imposter syndrome kicks in:

"They're going to realize I don't know what I'm doing"
"Everyone else seems to know more than me"
"I should have known this"

But: Everyone feels this way. The difference is confident people admit gaps instead of faking it.

You Think Expertise Means Always Having Answers

Wrong definition of expert: "Someone who knows everything about their field"

Right definition of expert: "Someone who knows what they know, what they don't know, and how to find answers"

Admitting you don't know IS expertise.

The Wrong Ways to Say "I Don't Know"

❌ The Rambling Non-Answer

Them: "What's the timeline for Phase 2?"

You: "Well, you know, timelines are always tricky, and there are a lot of variables, and we're still evaluating some dependencies, and it's hard to say exactly at this stage, but we're definitely making progress and should have more clarity soon..."

What they hear: "I have no idea and I'm trying to hide it."

Why it's bad:

Wastes everyone's time
Obviously evasive
Makes you look worse than just admitting it

❌ The Guess Presented as Fact

Them: "What's the ROI on that campaign?"

You: "About 15%" (You have no idea. You're guessing.)

What happens:

They make decisions based on your guess
Your wrong number causes problems
Later, when it's discovered you made it up, you've lost all credibility

Never present guesses as facts.

❌ The Deflection Blame

Them: "Why did the launch get delayed?"

You: "I don't know, you'd have to ask engineering about that."

What they hear: "I'm not taking responsibility for knowing what's happening with my project."

Why it's bad:

Sounds like passing the buck
If it's your job to know, saying you don't know AND not finding out is worse

❌ The Overly Apologetic Grovel

Them: "What's the conversion rate?"

You: "Oh my god, I'm so sorry, I should know this, I can't believe I don't have that number, I'm usually so prepared, this is embarrassing..."

What they hear: "I'm insecure and making this awkward for everyone."

One acknowledgment is professional. Five apologies is groveling.

The Right Way to Say "I Don't Know"

The Professional Formula

Structure:

Acknowledge directly (no hedging)
Explain why you don't know (if relevant)
State what you'll do (action step)
Provide timeline (when they'll have answer)

Example: "I don't have that number off the top of my head. I'll pull the report after this meeting and send it to you by 3pm today."

Why this works:

Honest and direct
Shows you know how to get the answer
Commits to timeline
Maintains credibility

Template #1: The Simple Acknowledge + Action

When asked something you don't know:

✅ "I don't know. Let me find out and get back to you by [time]."

✅ "I don't have that information right now. I'll check with [person/source] and update you today."

✅ "Good question—I don't know off the top of my head. I'll look into it and send you what I find."

Why it works:

Direct acknowledgment
Takes ownership of finding answer
Gives timeline

Template #2: The Partial Knowledge

When you know SOMETHING but not everything:

✅ "I know [what you do know], but I don't have the specific details on [what you don't know]. Let me get the full picture and follow up."

Example: "I know we shipped the first batch last week, but I don't have the exact count. Let me check with logistics and send you the numbers within the hour."

Why it works:

Shows you're not completely uninformed
Clarifies exactly what you're missing
Demonstrates you know where to get it

Template #3: The Expert Referral

When someone else is better positioned to answer:

✅ "That's outside my area—[name] on the [team] would be the expert on that. Want me to introduce you?"

✅ "I'm not the best person to answer that. [Name] handles [area] and would have more accurate information."

Why it works:

Acknowledges limits of your expertise
Points them to right person
Helpful rather than evasive

Template #4: The Boundary Setting

When you're not supposed to have that information:

✅ "I don't have visibility into that—it's outside my scope. [Department] would be able to help."

✅ "That's above my level. You'd need to speak with [role] for that information."

Why it works:

Clear about organizational structure
Not your responsibility to have this info
Directs to appropriate person

Real Examples: Wrong vs Right

Scenario: Boss Asks Technical Question You Don't Know

❌ WRONG

Boss: "What's causing the latency spike in production?"

You: "Um... I think it might be... database queries? Or maybe it's the cache? It could be a few different things. I'd have to... look at the logs? I'm not totally sure but I can probably figure it out at some point."

What's wrong:

Uncertain, rambling
Guessing without being clear it's a guess
No clear action plan
Vague timeline

✅ RIGHT

Boss: "What's causing the latency spike in production?"

You: "I don't know yet. I haven't had a chance to investigate. I'll check the monitoring dashboard and logs this afternoon and have an answer for you by end of day. If it's urgent, I can prioritize it and have a preliminary diagnosis in an hour."

What's right:

Clear admission
Explains why (haven't investigated yet)
Specific action plan
Two timeline options
Professional and confident

Scenario: Asked About Another Team's Work

❌ WRONG

Client: "When will the design revisions be ready?"

You: "Uh, I'm not sure. Design is kind of doing their own thing. They don't really keep me updated. You'd have to ask them, I guess?"

What's wrong:

Sounds like poor communication with team
Throws design under the bus
No help offered

✅ RIGHT

Client: "When will the design revisions be ready?"

You: "I don't have that timeline—design is tracking their own schedule. Let me check with Sarah and get back to you within the hour with an update."

What's right:

Direct acknowledgment
Doesn't blame design
Takes ownership of finding out
Specific timeline

When to Say You Don't Know vs When to Figure It Out First

Say "I Don't Know" When:

✅ The answer will take time to find

Better to commit to finding it than to keep them waiting

✅ Getting it wrong would cause problems

Admitting you don't know is safer than guessing

✅ It's completely outside your knowledge area

No point pretending

✅ They need accurate information immediately

Better they know you don't have it than wait for a guess

Figure It Out Before Admitting You Don't Know When:

✅ It's readily available information you should know

Check basic sources first (your notes, docs, dashboard)

✅ It takes 30 seconds to look up

"Let me pull that up quickly" > "I don't know"

✅ It's your core responsibility

If this is literally your job, saying you don't know without having tried is bad

✅ The meeting can pause for a moment

"Give me one second to check [source]" and get the answer now

How to Handle Follow-Up Questions You Also Don't Know

Them: "Okay, well do you at least know when it started?"

You (who also doesn't know this): "I don't have that detail either. Let me investigate the full picture—when it started, what's affected, and what's causing it—and send you a complete update by [time]."

Why this works:

Doesn't dig deeper into what you don't know
Bundles all unknowns into one action item
Shows you're thinking comprehensively

Special Situations

When You Should Have Known

Them: "What was last quarter's revenue?" (It's literally your job to track this)

Bad: ❌ "I don't know."

Better: ✅ "I should have that memorized and I don't. Give me 2 minutes to pull it up right now."

Why:

Acknowledges you should know
Fixes it immediately
Takes responsibility

When You're New

Them: "Where do we keep the project templates?"

You (3 days into job): "I'm still learning the systems—I haven't come across that yet. Could you point me to it, or is there a resource guide I should check?"

Why this works:

Context explains why you don't know
Asking for help is appropriate when new
Shows you want to learn

When Someone Is Testing You

Sometimes people ask questions to see if you'll bullshit or admit gaps.

Them: "What's our market share in the APAC region?"

You (suspect they already know): "I don't have those numbers. Do you have a source I should be referencing?"

Why this works:

Honest
Turns it into learning opportunity
Doesn't fall for trap of guessing

How to Build a Reputation for Knowing When You Don't Know

Always Follow Through

When you say "I'll get back to you by 3pm," do it.

If you consistently:

Admit what you don't know
Promise to find out
Actually deliver

People trust you MORE, not less.

Distinguish Between "I Don't Know" and "Nobody Knows"

Different situations:

✅ "I don't know, but I can find out" (information exists)

✅ "We don't have that data yet" (information doesn't exist yet)

✅ "Nobody knows for certain, but the best estimate is..." (inherent uncertainty)

Being clear about TYPE of unknown shows sophistication.

Document What You Learn

After you find out:

Share the answer
Document it somewhere team can find it
Update relevant docs

Next time someone asks, you DO know. And you've helped others.

What NOT to Do

❌ Never Make Up Data

Don't:

Guess at numbers
Estimate without saying it's an estimate
"Round" when you have no idea of the magnitude

If you get caught even once, you lose credibility on everything.

❌ Don't Say "I Don't Know" to Everything

If your answer to every question is "I don't know":

You look disengaged
You look like you're not doing your job
You need to be more prepared

It's about balance:

Know your core responsibilities
Admit gaps outside your area
Always have a plan to find out

❌ Don't Over-Explain Why You Don't Know

Bad: "I don't know because I was out sick last week and then when I came back I had a lot of emails to catch up on and I meant to check this but I got pulled into another meeting..."

Good: "I don't know. I'll find out and get back to you today."

Nobody needs your life story. Just fix it.

How to Reduce How Often You Don't Know

Anticipate Questions

Before meetings, think:

What might they ask?
Do I have those numbers/facts ready?
What documentation should I review?

Preparation reduces "I don't know" moments.

Build Good Information Systems

Make it easy to know:

Keep dashboards updated
Document key metrics
Have quick-reference docs
Know where to find information fast

"I don't know" → "Let me check" (30 seconds) → "Here it is"

Ask Proactively

Before someone asks you:

Check in with other teams
Stay updated on project status
Review metrics regularly
Anticipate information needs

Stay informed = fewer surprises.

The Confidence Framework

When you don't know something:

Don't panic - It's normal
Acknowledge directly - "I don't know"
Take ownership - "I'll find out"
Provide timeline - "By end of day"
Follow through - Actually do it
Update them - Deliver the answer

This pattern builds trust.

Why Admitting "I Don't Know" Builds Credibility

It Shows Integrity

People who can't say "I don't know":

Make up answers
Get caught in lies
Lose credibility permanently

People who admit gaps:

Are trusted to tell the truth
Are believed when they say they DO know
Have lasting credibility

It Shows Security

Insecure people: Must appear to know everything

Confident people: "I don't know. Here's how I'll find out."

Confidence comes from handling gaps professionally, not pretending they don't exist.

It Shows Good Judgment

Knowing the limits of your knowledge is a skill.

Better to say "I don't know" than:

Make a decision based on wrong information
Give bad advice
Mislead stakeholders

Good judgment includes knowing when to seek more information.

The 4 Tests for Saying "I Don't Know"

Before responding to a question you can't answer:

1. SIGNAL: Am I being clear and direct?

Or am I rambling and hedging?

2. OPPORTUNITY: Am I taking ownership of finding the answer?

Or am I just passing the buck?

3. RISK: Will guessing cause more problems than admitting I don't know?

Usually yes.

4. AFFECT: Am I handling this with confidence?

Or am I apologizing excessively?

Check Your Response

Not sure how to professionally say you don't know something?

Analyze your response free with 4Angles →

Write out what you plan to say. See how it scores on:

SIGNAL (Are you being clear?)
OPPORTUNITY (Are you taking ownership?)
RISK (Are you maintaining credibility?)
AFFECT (Do you sound confident or insecure?)

Get specific guidance on handling gaps in knowledge.

No signup required. Just instant analysis.

The Question You Can't Answer

You're in a meeting. Your boss asks you a question.

You have no idea what the answer is.

Your heart races. Everyone's looking at you.

What comes out:

"Um... well... I think maybe..."
[Fumbles through half-remembered information]
[Makes something up and hopes it's right]

What you're thinking: "If I say 'I don't know,' they'll think I'm incompetent."

The reality: Faking knowledge damages credibility far more than admitting you don't know.

But there's a right way and a wrong way to say "I don't know."

Why "I Don't Know" Feels Like Career Suicide

You Think It Makes You Look Stupid

Your fear: "They hired me to have answers. If I don't know, what good am I?"

The reality: Nobody knows everything. Pretending you do makes you look insecure and untrustworthy.

What actually looks stupid: Making up answers that are obviously wrong.

You're Worried About Being Found Out

Imposter syndrome kicks in:

"They're going to realize I don't know what I'm doing"
"Everyone else seems to know more than me"
"I should have known this"

But: Everyone feels this way. The difference is confident people admit gaps instead of faking it.

You Think Expertise Means Always Having Answers

Wrong definition of expert: "Someone who knows everything about their field"

Right definition of expert: "Someone who knows what they know, what they don't know, and how to find answers"

Admitting you don't know IS expertise.

The Wrong Ways to Say "I Don't Know"

❌ The Rambling Non-Answer

Them: "What's the timeline for Phase 2?"

What they hear: "I have no idea and I'm trying to hide it."

Why it's bad:

Wastes everyone's time
Obviously evasive
Makes you look worse than just admitting it

❌ The Guess Presented as Fact

Them: "What's the ROI on that campaign?"

You: "About 15%" (You have no idea. You're guessing.)

What happens:

They make decisions based on your guess
Your wrong number causes problems
Later, when it's discovered you made it up, you've lost all credibility

Never present guesses as facts.

❌ The Deflection Blame

Them: "Why did the launch get delayed?"

You: "I don't know, you'd have to ask engineering about that."

What they hear: "I'm not taking responsibility for knowing what's happening with my project."

Why it's bad:

Sounds like passing the buck
If it's your job to know, saying you don't know AND not finding out is worse

❌ The Overly Apologetic Grovel

Them: "What's the conversion rate?"

You: "Oh my god, I'm so sorry, I should know this, I can't believe I don't have that number, I'm usually so prepared, this is embarrassing..."

What they hear: "I'm insecure and making this awkward for everyone."

One acknowledgment is professional. Five apologies is groveling.

The Right Way to Say "I Don't Know"

The Professional Formula

Structure:

Acknowledge directly (no hedging)
Explain why you don't know (if relevant)
State what you'll do (action step)
Provide timeline (when they'll have answer)

Example: "I don't have that number off the top of my head. I'll pull the report after this meeting and send it to you by 3pm today."

Why this works:

Honest and direct
Shows you know how to get the answer
Commits to timeline
Maintains credibility

Template #1: The Simple Acknowledge + Action

When asked something you don't know:

✅ "I don't know. Let me find out and get back to you by [time]."

✅ "I don't have that information right now. I'll check with [person/source] and update you today."

✅ "Good question—I don't know off the top of my head. I'll look into it and send you what I find."

Why it works:

Direct acknowledgment
Takes ownership of finding answer
Gives timeline

Template #2: The Partial Knowledge

When you know SOMETHING but not everything:

✅ "I know [what you do know], but I don't have the specific details on [what you don't know]. Let me get the full picture and follow up."

Example: "I know we shipped the first batch last week, but I don't have the exact count. Let me check with logistics and send you the numbers within the hour."

Why it works:

Shows you're not completely uninformed
Clarifies exactly what you're missing
Demonstrates you know where to get it

Template #3: The Expert Referral

When someone else is better positioned to answer:

✅ "That's outside my area—[name] on the [team] would be the expert on that. Want me to introduce you?"

✅ "I'm not the best person to answer that. [Name] handles [area] and would have more accurate information."

Why it works:

Acknowledges limits of your expertise
Points them to right person
Helpful rather than evasive

Template #4: The Boundary Setting

When you're not supposed to have that information:

✅ "I don't have visibility into that—it's outside my scope. [Department] would be able to help."

✅ "That's above my level. You'd need to speak with [role] for that information."

Why it works:

Clear about organizational structure
Not your responsibility to have this info
Directs to appropriate person

Real Examples: Wrong vs Right

Scenario: Boss Asks Technical Question You Don't Know

❌ WRONG

Boss: "What's causing the latency spike in production?"

What's wrong:

Uncertain, rambling
Guessing without being clear it's a guess
No clear action plan
Vague timeline

✅ RIGHT

Boss: "What's causing the latency spike in production?"

What's right:

Clear admission
Explains why (haven't investigated yet)
Specific action plan
Two timeline options
Professional and confident

Scenario: Asked About Another Team's Work

❌ WRONG

Client: "When will the design revisions be ready?"

You: "Uh, I'm not sure. Design is kind of doing their own thing. They don't really keep me updated. You'd have to ask them, I guess?"

What's wrong:

Sounds like poor communication with team
Throws design under the bus
No help offered

✅ RIGHT

Client: "When will the design revisions be ready?"

You: "I don't have that timeline—design is tracking their own schedule. Let me check with Sarah and get back to you within the hour with an update."

What's right:

Direct acknowledgment
Doesn't blame design
Takes ownership of finding out
Specific timeline

When to Say You Don't Know vs When to Figure It Out First

Say "I Don't Know" When:

✅ The answer will take time to find

Better to commit to finding it than to keep them waiting

✅ Getting it wrong would cause problems

Admitting you don't know is safer than guessing

✅ It's completely outside your knowledge area

No point pretending

✅ They need accurate information immediately

Better they know you don't have it than wait for a guess

Figure It Out Before Admitting You Don't Know When:

✅ It's readily available information you should know

Check basic sources first (your notes, docs, dashboard)

✅ It takes 30 seconds to look up

"Let me pull that up quickly" > "I don't know"

✅ It's your core responsibility

If this is literally your job, saying you don't know without having tried is bad

✅ The meeting can pause for a moment

"Give me one second to check [source]" and get the answer now

How to Handle Follow-Up Questions You Also Don't Know

Them: "Okay, well do you at least know when it started?"

Why this works:

Doesn't dig deeper into what you don't know
Bundles all unknowns into one action item
Shows you're thinking comprehensively

Special Situations

When You Should Have Known

Them: "What was last quarter's revenue?" (It's literally your job to track this)

Bad: ❌ "I don't know."

Better: ✅ "I should have that memorized and I don't. Give me 2 minutes to pull it up right now."

Why:

Acknowledges you should know
Fixes it immediately
Takes responsibility

When You're New

Them: "Where do we keep the project templates?"

You (3 days into job): "I'm still learning the systems—I haven't come across that yet. Could you point me to it, or is there a resource guide I should check?"

Why this works:

Context explains why you don't know
Asking for help is appropriate when new
Shows you want to learn

When Someone Is Testing You

Sometimes people ask questions to see if you'll bullshit or admit gaps.

Them: "What's our market share in the APAC region?"

You (suspect they already know): "I don't have those numbers. Do you have a source I should be referencing?"

Why this works:

Honest
Turns it into learning opportunity
Doesn't fall for trap of guessing

How to Build a Reputation for Knowing When You Don't Know

Always Follow Through

When you say "I'll get back to you by 3pm," do it.

If you consistently:

Admit what you don't know
Promise to find out
Actually deliver

People trust you MORE, not less.

Distinguish Between "I Don't Know" and "Nobody Knows"

Different situations:

✅ "I don't know, but I can find out" (information exists)

✅ "We don't have that data yet" (information doesn't exist yet)

✅ "Nobody knows for certain, but the best estimate is..." (inherent uncertainty)

Being clear about TYPE of unknown shows sophistication.

Document What You Learn

After you find out:

Share the answer
Document it somewhere team can find it
Update relevant docs

Next time someone asks, you DO know. And you've helped others.

What NOT to Do

❌ Never Make Up Data

Don't:

Guess at numbers
Estimate without saying it's an estimate
"Round" when you have no idea of the magnitude

If you get caught even once, you lose credibility on everything.

❌ Don't Say "I Don't Know" to Everything

If your answer to every question is "I don't know":

You look disengaged
You look like you're not doing your job
You need to be more prepared

It's about balance:

Know your core responsibilities
Admit gaps outside your area
Always have a plan to find out

❌ Don't Over-Explain Why You Don't Know

Bad: "I don't know because I was out sick last week and then when I came back I had a lot of emails to catch up on and I meant to check this but I got pulled into another meeting..."

Good: "I don't know. I'll find out and get back to you today."

Nobody needs your life story. Just fix it.

How to Reduce How Often You Don't Know

Anticipate Questions

Before meetings, think:

What might they ask?
Do I have those numbers/facts ready?
What documentation should I review?

Preparation reduces "I don't know" moments.

Build Good Information Systems

Make it easy to know:

Keep dashboards updated
Document key metrics
Have quick-reference docs
Know where to find information fast

"I don't know" → "Let me check" (30 seconds) → "Here it is"

Ask Proactively

Before someone asks you:

Check in with other teams
Stay updated on project status
Review metrics regularly
Anticipate information needs

Stay informed = fewer surprises.

The Confidence Framework

When you don't know something:

Don't panic - It's normal
Acknowledge directly - "I don't know"
Take ownership - "I'll find out"
Provide timeline - "By end of day"
Follow through - Actually do it
Update them - Deliver the answer

This pattern builds trust.

Why Admitting "I Don't Know" Builds Credibility

It Shows Integrity

People who can't say "I don't know":

Make up answers
Get caught in lies
Lose credibility permanently

People who admit gaps:

Are trusted to tell the truth
Are believed when they say they DO know
Have lasting credibility

It Shows Security

Insecure people: Must appear to know everything

Confident people: "I don't know. Here's how I'll find out."

Confidence comes from handling gaps professionally, not pretending they don't exist.

It Shows Good Judgment

Knowing the limits of your knowledge is a skill.

Better to say "I don't know" than:

Make a decision based on wrong information
Give bad advice
Mislead stakeholders

Good judgment includes knowing when to seek more information.

The 4 Tests for Saying "I Don't Know"

Before responding to a question you can't answer:

1. SIGNAL: Am I being clear and direct?

Or am I rambling and hedging?

2. OPPORTUNITY: Am I taking ownership of finding the answer?

Or am I just passing the buck?

3. RISK: Will guessing cause more problems than admitting I don't know?

Usually yes.

4. AFFECT: Am I handling this with confidence?

Or am I apologizing excessively?

Check Your Response

Not sure how to professionally say you don't know something?

Analyze your response free with 4Angles →

Write out what you plan to say. See how it scores on:

SIGNAL (Are you being clear?)
OPPORTUNITY (Are you taking ownership?)
RISK (Are you maintaining credibility?)
AFFECT (Do you sound confident or insecure?)

Get specific guidance on handling gaps in knowledge.

No signup required. Just instant analysis.

How to Say "I Don't Know" Without Looking Incompetent

The Question You Can't Answer

Why "I Don't Know" Feels Like Career Suicide

You Think It Makes You Look Stupid

You're Worried About Being Found Out

You Think Expertise Means Always Having Answers

The Wrong Ways to Say "I Don't Know"

❌ The Rambling Non-Answer

❌ The Guess Presented as Fact

❌ The Deflection Blame

❌ The Overly Apologetic Grovel

The Right Way to Say "I Don't Know"

The Professional Formula

Template #1: The Simple Acknowledge + Action

Template #2: The Partial Knowledge

Template #3: The Expert Referral

Template #4: The Boundary Setting

Real Examples: Wrong vs Right

Scenario: Boss Asks Technical Question You Don't Know

❌ WRONG

✅ RIGHT

Scenario: Asked About Another Team's Work

❌ WRONG

✅ RIGHT

When to Say You Don't Know vs When to Figure It Out First

Say "I Don't Know" When:

Figure It Out Before Admitting You Don't Know When:

How to Handle Follow-Up Questions You Also Don't Know

Special Situations

When You Should Have Known

When You're New

When Someone Is Testing You

How to Build a Reputation for Knowing When You Don't Know

Always Follow Through

Distinguish Between "I Don't Know" and "Nobody Knows"

Document What You Learn

What NOT to Do

❌ Never Make Up Data

❌ Don't Say "I Don't Know" to Everything

❌ Don't Over-Explain Why You Don't Know

How to Reduce How Often You Don't Know

Anticipate Questions

Build Good Information Systems

Ask Proactively

The Confidence Framework

Why Admitting "I Don't Know" Builds Credibility

It Shows Integrity

It Shows Security

It Shows Good Judgment

The 4 Tests for Saying "I Don't Know"

1. SIGNAL: Am I being clear and direct?

2. OPPORTUNITY: Am I taking ownership of finding the answer?

3. RISK: Will guessing cause more problems than admitting I don't know?

4. AFFECT: Am I handling this with confidence?

Check Your Response

Related Reading

Ready to Analyze Your Message?

How to Say "I Don't Know" Without Looking Incompetent

The Question You Can't Answer

Why "I Don't Know" Feels Like Career Suicide

You Think It Makes You Look Stupid

You're Worried About Being Found Out

You Think Expertise Means Always Having Answers

The Wrong Ways to Say "I Don't Know"

❌ The Rambling Non-Answer

❌ The Guess Presented as Fact

❌ The Deflection Blame

❌ The Overly Apologetic Grovel

The Right Way to Say "I Don't Know"

The Professional Formula

Template #1: The Simple Acknowledge + Action

Template #2: The Partial Knowledge

Template #3: The Expert Referral

Template #4: The Boundary Setting

Real Examples: Wrong vs Right

Scenario: Boss Asks Technical Question You Don't Know

❌ WRONG

✅ RIGHT

Scenario: Asked About Another Team's Work

❌ WRONG