Don't Call Out Gaps in Public

The Room Changes When You Do It

You're in a team meeting. Someone makes a mistake, misses something obvious, presents work that isn't ready. And you address it right there, in the room, in front of everyone.

Maybe you're thinking about efficiency. Get it corrected once, everyone hears it, no need for a separate conversation. Maybe you're not thinking at all and it just comes out. Either way, the outcome is the same.

You didn't give feedback. You made an example of someone.

And here's what you can't see from the front of the room: everyone else just learned something, but it has nothing to do with the mistake. What they learned is what happens when they fall short in your presence. They learned to hide things from you, to over-polish before they bring you anything, to stay quiet when they're uncertain rather than risk being the next example. The person you called out learned something too. They learned that your room isn't safe, and that information will sit in their gut every single time they walk into it.

That's the cancer. One public callout, and it spreads through the whole tissue of the team.

Why Managers Do It Anyway

I want to be honest about why this happens, because it's usually not malicious.

Sometimes it's impatience. The feedback is relevant to everyone in the room, and the temptation to handle it live is real. Sometimes it's frustration leaking out, and the manager doesn't fully realize how sharp it sounds until it's already in the air. Sometimes it's a misguided belief that public accountability is a motivator, that naming a gap in front of peers creates positive pressure.

That last one is the most dangerous belief because it has just enough surface logic to feel true. Peer accountability works in some contexts. Team retrospectives, shared goal reviews, group commitments. But that is categorically different from a manager surfacing an individual's specific competency gap in front of the group. One is collective reflection. The other is exposure.

And people know the difference. The person on the receiving end knows it immediately. So does everyone watching.

What Actually Happens to the Person

I've managed a lot of people across a long career, and I've watched public callouts play out enough times to know the pattern. The immediate reaction is usually compliance. The person nods, adjusts, maybe even thanks you. Don't mistake that for the feedback landing well.

What's actually happening underneath is closer to a threat response. Their nervous system is managing the social threat of being seen as inadequate in front of peers. That takes cognitive and emotional bandwidth. The part of their brain that would process your feedback and grow from it is busy managing the shame.

Shame and growth don't coexist well. Shame closes people down. It makes them more concerned with protecting their reputation than improving their performance. You get surface behavior changes, but you lose the internal buy-in that produces lasting development. They stop bringing you problems early. They start polishing their presentation of reality to you. They optimize for not being caught rather than for getting better.

And here's the thing: you may never see it directly. They'll seem fine. The gap you called out might even close, temporarily, in the specific context where you called it out. But the trust is eroded, and trust is what makes feedback actually work over time. You've traded a short-term correction for a long-term reduction in your ability to develop that person.

The Private Conversation Does Something Different

When you call something out privately, you change the entire dynamic of the exchange.

The person isn't managing social threat. They're just talking to you. Their defenses are lower. They can hear you more clearly. They can ask questions without looking weak. They can admit they're struggling without that admission being recorded in the social memory of the team. That's the environment where real development happens.

Private feedback also gives you more room to get it right. In a meeting, you're working with whatever came out of your mouth, no edits. One-on-one, you can be precise. You can lead with what you observed, give context for why it matters, and ask what was going on for them before you assume you understand the root cause. That last part is more important than most managers realize. Half the time, what looks like a skill gap is actually a context problem, a resource problem, or a communication failure on your end. You only find that out in a real conversation, not in a public correction.

Point being, the private conversation isn't the soft path. It's the more demanding one. You have to prepare it, structure it, sit with someone and actually work through something. That's harder than dropping a correction into a meeting. It's also the only version that produces durable growth.

Name It Privately, Grow It Privately

If the gap is real and worth addressing, it's worth a real conversation. Not a hallway comment on the way out of the meeting. Not a Slack message because you're too busy for a call. An actual sit-down where you can look at someone and work through it together.

Some things worth getting right in that conversation. Lead with what you observed, specifically. Not "your presentation felt underprepared" but "the data on slide four didn't have a source, and when asked about methodology you couldn't answer the question." Specific observations don't trigger the same defensiveness as general judgments. They're harder to argue with, and they give the person something concrete to work on.

Then ask before you prescribe. Find out what was happening for them. You might learn something that changes your read of the situation. And even if it doesn't, asking communicates that you're invested in understanding, not just delivering a verdict.

Last, make it forward-looking. The point of the conversation isn't to establish that they failed. It's to close the gap. What does better look like? What support do they need? What's the next opportunity to try again? That's the part of the conversation that actually produces development, and it only happens when the person isn't busy managing embarrassment.

What to Do When the Group Needs to Hear Something

Here's the legitimate question this raises: what about mistakes that affect the whole team? What if the same issue is happening across multiple people, or if the situation has real consequences that the group needs to understand?

Address the issue with the group, not the person.

"We had a situation this week where deliverables went out without the client approval step being completed, and I want to make sure we all understand why that step matters." That's legitimate group feedback. You're addressing a process, a standard, a shared expectation. You're not putting one person's face on a failure.

If one specific person needs to hear more, they get a separate conversation. You can do both. The group conversation handles the shared lesson. The private conversation handles the individual development. Those are different objectives and they deserve different formats.

The Standard Worth Holding

Your job as a manager is to make your team better. Not to make your meetings more efficient, not to signal that you hold high standards, not to show that you noticed the mistake. To actually make people better over time.

Public callouts feel like feedback. They register as accountability. But what they actually produce is a more careful, more guarded, more defensive team that gets harder to develop with every example you make.

Name it privately. Work it privately. The growth follows.