Available on Spotify, Apple Podcasts, and wherever you get your podcasts.
Politeness has a way of making rooms feel calm. Meetings run smoothly. People sound agreeable. And it can feel like things are working.
But I see this all the time: nothing actually changes.
The issue doesn’t go away. It just gets harder to deal with later.
This isn’t about giving people permission to be rude. It’s about what happens when politeness becomes more important than talking about the thing that’s in the way.
Who Decides What “Polite” Means
Politeness is a construct. And most of the time, the people who get to define it are the people with the most power.
That’s when “be polite” starts to mean:
- don’t push back on the boss’s idea
- don’t question a decision in the room
- don’t hold a coworker accountable if it’s uncomfortable
I’ve watched good ideas die quietly this way. Not because they were bad ideas, but because saying them out loud felt risky. So people wait. They soften. They water things down. And by the time the feedback shows up, the moment has passed.
If you want different results, you have to make it normal to challenge ideas. Pushback can’t be rare or heroic. It has to be routine.
When People Start Picking at the Words
This is the moment where progress usually stalls.
Someone finally says the hard thing. And instead of dealing with what they said, the room starts picking at how they said it.
“You didn’t have to say it like that.”
“You could’ve been more polite.”
What they’re really asking for is sugar coating. Icing. Honey on every word.
And when we do that, we shift the focus away from the problem and onto comfort. The message gets lost. Accountability disappears. Everyone leaves the meeting polite and nothing gets fixed.
If you catch yourself splitting hairs about phrasing, pause. Ask why this is making you so uncomfortable that tone suddenly matters more than the content.
Sugar Coating Slows Everything Down
By the time feedback gets smoothed into something completely safe, the chance to act is usually gone.
Real work has edges. Sometimes feedback is sharp because the issue is sharp. That doesn’t make it wrong.
Plain language helps:
- Say what’s not working.
- Say why it matters.
- Say what needs to change.
- Say who’s doing it and by when.
“Maybe consider” rarely moves anything forward. Talking about the thing does.
What Leaders Teach Without Realizing It
Leaders set the tone whether they mean to or not.
If people watch you get defensive, they’ll stop being honest. If they see you punish discomfort, they’ll stay polite. If they see you thank clarity, they’ll use it.
When someone gives you direct feedback, start with thank you. Reflect what you heard. Take a visible step. If something landed hard, separate delivery from data. Keep the insight. Coach the delivery later.
Over time, people learn what’s actually rewarded in the room.
Cleaner Conversations Move Work Faster
Directness isn’t about being louder. It’s about being cleaner.
Simple language helps:
- “For this goal, the risk is X. I recommend Y.”
- “I’m going to be direct so we can move forward: this is blocking that. Let’s fix it by Friday.”
This kind of clarity isn’t an attack. It’s a service. It saves time. It helps teams move.
Politeness kills progress when it keeps us from telling the truth. Talking about the thing is how work actually gets done.
Listen to the Episode
I unpack this more in the latest episode of Five with Fry. We talk about how politeness shows up at work, how it gets used to shut conversations down, and what it looks like to stop sanding down the truth and deal with it directly.
If this made you uncomfortable, listen to the episode.
That’s probably the point.
