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: 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. Multiple independent Reddit threads from unrelated communities, including r/cybersecurity, r/managers, and general career subreddits, describe managers correcting or mocking a specific employee’s mistake in front of the full team, with commenters consistently naming it “public shaming” and describing the same downstream effect: people stop speaking up.

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, and afterward other team members quietly stop flagging their own mistakes early.

Why they do it: It is a fast, visible way to assert authority and enforce compliance across the whole group at once, using one person’s exposure to control everyone else’s behavior, often at the cost of the very error-reporting that would prevent bigger problems later.

How to protect yourself:

• 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?”
• 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, Covert Digs / Dog Whistling, Workplace Incivility.

Sources:

• r/cybersecurity: “Upper management shaming analyst’s mistake in meeting”, a thread naming and describing the exact dynamic in a security-team context.
• r/managers: “Colleague called out team member publicly in meeting”, a management-focused subreddit discussing how to handle a peer doing this to a direct report.
• Amy Edmondson, “Psychological Safety and Learning Behavior in Work Teams,” Harvard Business School, the foundational paper establishing that fear of humiliation for mistakes suppresses team learning and error-reporting.

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. “Public shaming” itself is a plain-language description rather than a technical term, but the mechanism it describes, and its damage to team morale and error-reporting, is well studied.