Public Shaming (in Meetings)

One-liner: Criticizing or humiliating someone in front of the group instead of privately, so the point is the audience, not the feedback.

Also known as / related terms: Public humiliation, calling someone out, public criticism, dressing someone down in front of the team.

What it is

The audience is the punishment.

A manager or colleague delivers criticism, correction, or ridicule in a group setting, a team meeting, a shared channel, a client call, where it could easily have been handled one-on-one. Unlike coded put-downs, everyone in the room understands exactly what is happening and who it is aimed at. The humiliation is overt, and the audience is the point: it signals dominance to the target and a warning to everyone watching. This is grounded in organizational research on psychological safety by Harvard’s Amy Edmondson, whose work found that teams perform better and learn faster when people believe they will not be humiliated or punished for mistakes or questions, and that fear of public exposure specifically shuts down the reporting and discussion that catches problems early. Worker testimony from unrelated online communities, including r/cybersecurity, r/managers, and general career forums, independently describes managers correcting or mocking a specific employee’s mistake in front of the full team, consistently naming it “public shaming” and describing the same downstream effect: people stop speaking up.

Psychologists Tangney and Dearing’s foundational 2002 work distinguishes shame from guilt in a way that explains why the public setting makes the damage worse, not just more embarrassing. Guilt is about a specific bad act, “I did a bad thing,” and it motivates repair: apologizing, fixing the mistake, doing better. Shame is about the whole self, “I am a bad person,” and it motivates hiding, defensiveness, and anger instead, because there’s no specific act left to repair, only a self to protect. The same error, corrected privately, tends to stay guilt, fixable and forward-looking. Corrected in front of an audience, it tends to convert into shame, and shame is what drives people to hide their next mistake rather than raise it.

What it looks like (workplace)

In a weekly status meeting, a manager reads out one engineer’s bug by name in front of the whole team (“so-and-so broke prod again”) rather than raising it privately. Two sprints later, a different engineer notices a real configuration risk and sits on it for four days before finally flagging it, quietly, in a private message, costing the team far more time than the original bug ever did.

How it actually unfolds

1. Pretext selection. A real but minor error gets chosen: its realness is what provides cover; there’s genuinely something to point at.
2. Staging. The venue, a team meeting, a shared channel, a client call, is chosen for its audience, not for problem-solving. No path to correction gets offered, because fixing the issue was never actually the function of the moment.
3. The exposure. The person is named specifically, sometimes with a laugh line attached. Every option left to them is bad: defending themselves reads as defensive, absorbing it silently reads as confirming guilt, and objecting to the venue itself risks Labeling as someone who “can’t take feedback,” or a manufactured confrontation via Emotional Trap Setting if they push back too hard.
4. The broadcast payoff. The audience, not just the target, learns that mistakes are dangerous to admit out loud, and Edmondson’s research documents exactly what follows: error-reporting drops across the team, feeding directly into Culture of Fear and, in its more ritualized full-dress form, The Degradation Ceremony.

Stage 1 costs nothing yet: a real error is easy to justify raising. Stage 2 costs the target the chance to fix it quietly. Stage 3 costs them dignity with no safe response available. Stage 4 costs the whole team the early warnings that public shame teaches everyone to stop giving.

Why they do it

It is a fast, visible way to assert authority and enforce compliance across the whole group at once. One person’s exposure controls everyone else’s behavior, often at the cost of the very error-reporting that would prevent bigger problems later, and because public exposure specifically converts a fixable guilt response into a defensive shame response, the damage compounds well past the original mistake.

How to protect yourself

You can move it out of the room without making a scene.

• If it happens to you, ask to take it offline in the moment: “Happy to go through this in detail, can we do it after the meeting?” Moving the conversation out of the room is also, functionally, converting shame back into addressable guilt.
• Document the pattern, dates, what was said, who was present. A single incident is awkward. A pattern is a management problem.
• Where possible, raise concerns in writing or in one-on-ones rather than open forums if you suspect a manager uses meetings this way.
• If you are a bystander, a private check-in with the targeted colleague afterward matters more than it seems.

Cross-links: Culture of Fear, the organizational condition this tactic manufactures at scale; The Degradation Ceremony, the ritualized, full-dress version of the same exposure; Covert Digs / “Dog Whistling”, the covert sibling delivering the same aggression through deniable means; Baiting, when public shaming doubles as a provocation to manufacture a reaction; Emotional Trap Setting, the trap that springs if the target pushes back; Workplace Incivility, the low-grade, ambient version of the same spectrum.

Sources:

Label note: Established organizational-behavior research, Edmondson’s psychological safety line of work is peer-reviewed and widely replicated, applied to a specific, informally-named tactic, and strengthened here by Tangney and Dearing’s separately established shame-versus-guilt research. “Public shaming” itself is a plain-language description rather than a technical term, but the mechanisms it describes, and its damage to team morale and error-reporting, are well studied.