Polite Ways to Tell Someone They're Stupid at Work
This post contains Amazon affiliate links. If you buy through them, we may earn a small commission at no extra cost to you.
Todd Winfield writes the HR-Approved workplace humor series.
Someone in the team channel asks where the onboarding file is. It's pinned right above their message, and they're the one who pinned it.
The polite way to tell someone they're stupid at work is to never call the person anything. Point at the decision instead, and phrase it so they can find the mistake themselves: "Help me understand the thinking here." Below are 48 polite ways to tell someone they're stupid at work, sorted from "they might just be tired" to "bless your heart." Every line passes the HR test. HR will probably still know what you meant.
Quick answer: what's the corporate way to say "you're stupid"?
These are the classics. Each one is polite on the surface, and everyone in the room knows what it means.
| What you say | What it really means |
|---|---|
| "Let's align on the basics first." | You've skipped the basics. All of them. |
| "That's an interesting approach." | Never do that again. |
| "I'll send over some background reading." | You have no idea what you're talking about. |
| "Help me understand the thinking here." | There was no thinking here. |
| "Let's not reinvent the wheel." | Someone already solved this, and you ignored them. |
| "Happy to pair on this." | I'm going to watch you do it so it doesn't happen again. |
| "Maybe we start with what problem we're solving?" | You're solving the wrong one. |
| "Great question. It's on page one." | No translation needed. |
| "Let's run that by legal first." | That idea is terrifying. |
| "Thanks, I'll take it from here." | Please step away from the project. |
The one rule: call the decision, never the person
Every line on this page follows the same rule. You never call a person stupid. You only point at what they did: the plan, the formula, the reply-all, the file they edited that everyone stopped using in August.
That's not only good manners. Calling a coworker stupid is a personal remark, and personal remarks get reported. "This plan has a gap" is feedback about the work, and nobody gets written up for that.
It's also the only way any of this actually works. Insult a person and they get defensive. Point at the decision and there's a chance they fix it.
Level 1: The gentle nudge
For first offenses, Mondays and people who might genuinely just be tired. Assume good intent. Most mistakes are only mistakes.
| What you say | Use it when |
|---|---|
| "Not sure if you saw the pinned message, but it covers this." | They asked a question the channel already answered. |
| "Quick sanity check before this goes out?" | You've spotted the error and want them to find it themselves. |
| "Just a heads-up: the client spells it with a K." | The fix is faster than the conversation. |
| "Easy mix-up. The template's in the shared drive." | It's the first time. Only the first time. |
| "Want me to grab you the link?" | The link has been sent four times. |
| "I think there's a newer version of that file." | They're editing v3. Everyone else is on v7. |
| "Might be worth a second look at cell D14." | The formula's broken, and you know exactly where. |
| "Totally understandable. It's a confusing process." | It isn't. But it's Monday, and you're generous. |
"Want me to grab you the link?" sounds like an offer to help. It's really the last time you'll send that link.
Level 2: The raised eyebrow
The second time it happens. The words are still polite, but the pause before them isn't.
| What you say | What it really means |
|---|---|
| "Oh, interesting." | Not interesting. |
| "Remind me how we got here?" | Nobody knows how we got here, least of all you. |
| "Is that the latest guidance?" | It was the latest guidance in 2019. |
| "Hmm. Let's sleep on it." | Let's let this idea die quietly overnight. |
| "Have we considered the opposite?" | The opposite is the right answer. |
| "I'd love to see the data on that." | There is no data on that. |
| "That's one option." | That's the wrong option. |
| "Let's make sure we're solving for the customer." | You're solving for yourself. |
"Let's sleep on it" is the kindest way to kill an idea. Nobody brings it up the next day, and nobody has to say no.
Level 3: The documented sigh
Some people have to see it in writing. The written version helps them, and it also leaves a record if the same mistake keeps happening.
| What you say | What it really means |
|---|---|
| "To clarify my earlier point:" | My earlier point was already clear. |
| "Highlighting the relevant section below." | In yellow. Because nothing else has worked. |
| "I've added an FAQ to the top of the doc." | I've answered your questions publicly, permanently. |
| "Adding a screenshot for reference." | Here's proof. |
| "Happy to jump on a quick call to clarify." | Writing it down has failed us both. |
| "Let's make sure we're all working from the same version." | You aren't. |
| "Noting this here for the record." | For the record. And for later. |
The FAQ at the top of the doc is the best thing on this list. It helps the next new hire, it stops the same question coming back, and everyone else on the team quietly knows who it was written for.
For more of the email side ("per my last email" and its relatives), see our full list of HR-approved ways to say things at work.
Level 4: Bless your heart
Sweet on the surface, and everyone knows what's underneath. These work best said warmly, with a straight face.
| What you say | What it really means |
|---|---|
| "Bless your heart." | The whole sentence in three words. |
| "Well, that's certainly a choice." | A bad one. |
| "Bold strategy." | It won't work. |
| "I admire your confidence." | You should have less of it. |
| "You've clearly put a lot of thought into this." | You put no thought into this. |
| "What a creative interpretation of the brief." | You didn't read the brief. |
| "I never would have thought of that." | No reasonable person would. |
| "That's… a take." | The pause is doing all the work. |
Use this level carefully. Said with a smile to a peer who shares your sense of humor, it's a bonding moment. Said in front of the whole team, it's an incident.
Level 5: The meeting-safe mic drop
For when the bad idea is about to become everyone's problem. These are calm and professional, and they bring the conversation back to the facts.
| What you say | What it really means |
|---|---|
| "Let's take a step back." | We've walked off a cliff. |
| "What does success look like here?" | You can't answer this, and now everyone knows it. |
| "I'll let the numbers speak for themselves." | The numbers are on my side. |
| "Let's revisit when we have more information." | When you have any information. |
| "Can we pressure-test that assumption?" | Your assumption won't survive the test. |
| "Let's table this until the right people are in the room." | You aren't the right people. |
| "We owe it to the team to get this right." | You're about to get this wrong in front of the team. |
"What does success look like here?" is the most useful question in any meeting. A good plan has an answer ready. A bad plan goes quiet, and nobody has to say a word.
What do you say when a coworker does something dumb?
A quick reference for the moments that come up most.
| The situation | The line |
|---|---|
| They asked something already answered in the channel | "Not sure if you saw the pinned message, but it covers this." |
| Same mistake, third time | "Happy to pair on this." |
| They presented a plan with no plan in it | "What does success look like here?" |
| They clearly didn't read the brief | "What a creative interpretation of the brief." |
| They're confidently wrong in front of a client | "Let's run that by legal first." |
| They spent two hours editing the wrong file | "I think there's a newer version of that file." |
Which "polite" phrases will get you reported?
Some phrases sound polite and land like a slap. Cut these five:
- "No offense, but…" Everyone braces, because offense is on its way.
- "With all due respect…" Everyone hears "no respect is due."
- "Let me explain it more slowly." This is just calling them stupid, slowly.
- "Even the intern knows this." Now the intern is offended too.
- "I'm sure you did your best." It sounds like the opening of a performance review.
Why this only works between peers
Here's the important part. Every line on this page works sideways, between coworkers at the same level. Between peers, a "bless your heart" is solidarity. From a manager to someone on their team, it's a power imbalance, and it can end up in a meeting with HR.
If you manage people, you need the version that actually changes behavior: specific, private and about the work. "The numbers in slide 6 don't match the source. Can you rework them by Thursday?" isn't funny, but it works. Save the jokes for your peers.
And if one coworker's mistakes keep landing on your desk, it's no longer a phrasing problem. Write down what happened, talk to them directly, and bring in your manager if it keeps affecting your work. Our office politics survival guide has scripts for when it gets that far.
Questions people actually ask
How do you politely tell someone they're stupid?
You don't call them anything. You point at what they did. "Help me understand the thinking here" or "Have we considered the opposite?" lets them find the problem themselves, and it keeps you clear of anything HR could flag.
How do you respond when a coworker is confidently wrong in a meeting?
Ask a question that brings the facts back: "What does success look like here?" or "Can we pressure-test that assumption?" You stay calm, the room checks the facts, and you never have to say "you're wrong" in front of everyone.
Is it ever OK to call a coworker stupid?
No. A remark about someone's intelligence is personal, and personal remarks can be reported. Talk about the decision, the document or the plan, never the person. You'll make the same point, and you'll keep your job.
How do you deal with a coworker who keeps making the same mistake?
First, offer to pair with them on it once. Then write the steps down somewhere they can find them, like a checklist or an FAQ at the top of the doc. If it still happens and it's affecting your work, raise it with your manager, with examples.
Is there a book of HR-approved ways to tell coworkers they're stupid?
Yes. HR Approved Ways to Tell Co-Workers They're Stupid by Todd Winfield is the most-reviewed book in the HR Approved series, and every line in it is clean enough to say out loud at work. It's on Amazon.
Start here
If someone came to mind while you were reading, you already know who this is for.
- For the coworker who's surrounded by people who make it hard to stay polite: HR Approved Ways to Tell Co-Workers They're Stupid. Give it peer to peer, never manager to employee.
- For the relentlessly diplomatic one: HR-Approved Ways to Say Things I Can't Say Out Loud at Work. The free version is our list of HR-approved ways to say things at work.
- For the new manager who needs to give real feedback without losing their mind: HR Approved Ways to Lead Without Losing Your Mind.
Buying for the office gift exchange? Our funny coworker gifts guide sorts every pick by Secret Santa budget.