Jon's Job Blog

The correction happened in a team stand-up. My work—something I'd built, tested, and delivered—was critiqued in front of the group. Not in the way that healthy teams surface problems: specific, constructive, focused on the work. This was something else. The critique was directed at me as much as at the output. The subtext was legible to everyone in the virtual room: this is what happens when your work isn't good enough. This is what it looks like to fall short.

The actual feedback might have been useful. I'll never know, because I couldn't process it. What I was processing instead was the social dimension—the colleagues watching, the power dynamic being demonstrated, the shame response that had already flooded my nervous system before the substantive content of the criticism could register. By the time the meeting ended, I couldn't have told you what specifically needed to change about the work. I could tell you exactly how it felt to be corrected in front of peers. The feedback failed at its stated purpose—improving the work—and succeeded at its actual purpose: establishing hierarchy.

This essay is about that distinction. About the gap between feedback that develops people and feedback that disciplines them. About what happens when organizations adopt the language of transparency and accountability but implement them as surveillance and public correction. About how "radical candor" becomes radical cruelty when it's deployed without empathy, and how the people most damaged by this system are the ones least equipped to push back against it.

Shame research makes the neurological mechanism clear. Public criticism doesn't just deliver information—it activates the brain's threat detection system. The social pain of being publicly humiliated registers in the same neural pathways as physical pain. The person being corrected isn't failing to receive the feedback. Their nervous system is prioritizing survival over learning. The cortisol flooding their system is shutting down the prefrontal cortex functions—reasoning, perspective-taking, creative problem-solving—that would be necessary to actually use the feedback constructively. The public format doesn't just feel bad. It biologically prevents the feedback from achieving its stated goal.

For neurodivergent employees—where Rejection Sensitive Dysphoria already means the emotional response to criticism is neurologically amplified—the effect is exponential. What registers as uncomfortable for a neurotypical person can register as catastrophic for someone with ADHD. Not because of emotional weakness, but because of neurological wiring that processes social rejection with disproportionate intensity. The public feedback system isn't just inequitable in its effects. It's architecturally hostile to the cognitive diversity that organizations claim to value.

The Correction Performance

Public criticism in workplace settings functions differently than private criticism, and the difference isn't just about comfort. It's about what the criticism is actually accomplishing.

Private feedback—delivered one-on-one, focused on specific behavior, oriented toward improvement—serves the person receiving it. It gives them information they can use without requiring them to simultaneously manage the social consequences of being seen as deficient. It preserves the relationship between the feedback giver and receiver. It treats the gap between current performance and desired performance as a problem to solve collaboratively, not a deficiency to display.

Public criticism does something different. It demonstrates power. When a manager critiques an employee's work in a team meeting, the primary audience isn't the person being corrected—it's everyone else. The message isn't "here's how to improve." The message is "here's what happens if you don't meet the standard." The correction is a performance, and the employee being corrected is the prop. Their embarrassment isn't a side effect. It's the mechanism through which the lesson is transmitted to the broader group.

Kim Scott's "Radical Candor" framework—which became enormously influential in corporate culture over the past decade—was supposed to address this. The framework distinguishes between caring personally and challenging directly, arguing that good feedback requires both. But in practice, many organizations adopted the "challenging directly" part and dropped the "caring personally" part. What remained was the license to be blunt without the obligation to be kind. Radical candor became radical correction, and the "radical" part gave it a veneer of progressive management philosophy that made it harder to challenge.

In the teams I worked with at PPG, this dynamic played out consistently. Corrections were public. Praise, when it came, was private or generic—a brief mention in a team email, an acknowledgment so formulaic it could have been automated. The asymmetry created an ambient anxiety that pervaded every interaction. You knew that mistakes would be visible. You knew that success would be invisible. The rational response to that asymmetry is what every team member eventually learned: optimize for not being noticed rather than for doing your best work.

The asymmetry also distorted the team's understanding of reality. When criticism is public and praise is absent, the team develops a skewed perception of its own competence. Even high-performing team members start to doubt themselves because the only feedback that gets airtime is negative feedback. You could deliver excellent work for weeks and hear nothing. One error would be surfaced in a stand-up for the entire team to witness. Over time, the silence around good work becomes its own message: adequate is the ceiling. The only feedback that matters is the kind that tells you you've fallen below it.

Identity as Dismissal

There's a specific version of public criticism that goes beyond work quality and targets identity. I experienced this as comments about my rural background—the kind of casual stereotyping that frames people from small towns and rural areas as unsophisticated, slow, or out of their depth in professional environments. "Bumpkin" assumptions, delivered with the kind of humor that insulates the speaker from accountability because "it's just a joke" or "I'm just being honest."

This is identity used as categorical dismissal. My input wasn't wrong—it was irrelevant because of where I was from. The message wasn't "your analysis has a flaw." It was "someone like you wouldn't understand this." The criticism bypassed the substance entirely and went straight to the person, establishing a social hierarchy based on geography, education pedigree, and cultural affiliation rather than the quality of the work itself.

Geographic stereotyping operates differently from other forms of bias because it's rarely recognized as bias at all. Comments about rural backgrounds, small-town origins, or regional accents are treated as harmless observation rather than prejudice. Nobody files an HR complaint about being called a bumpkin. Nobody identifies "geographic discrimination" as a protected category worth monitoring. But the functional effect is identical to any other form of identity-based dismissal: the person's contributions are filtered through an assumption about their category before being evaluated on their merits. The assumption—that rural means simple, that small-town means limited, that non-coastal means out of touch—forecloses engagement before engagement begins.

What made this particularly absurd in my case was that the perspective being dismissed—systems thinking, practical problem-solving, the ability to see through organizational complexity to the underlying structural issues—was arguably strengthened by a background outside the corporate mainstream. Forestry training teaches you to think in systems. Rural pragmatism teaches you to evaluate claims against observable reality rather than accepting institutional narratives at face value. The very qualities that were being stereotyped as deficiency were qualities the organization would have benefited from if it had evaluated them on their merits rather than their origin.

For someone already managing the cognitive load of ADHD masking—already expending significant energy to present as competent in neurotypical terms—this kind of identity-based dismissal hits differently. It's not just a professional setback. It activates the Rejection Sensitive Dysphoria I described in Essay 8, triggering an emotional response disproportionate to the surface-level interaction. A casual "bumpkin" joke lands like an existential verdict. The shame response floods the system, and the rest of the meeting—the rest of the day, sometimes—is spent managing the emotional fallout rather than doing productive work.

The strategic input I could have offered—the pattern recognition that comes from seeing systems differently, the outsider perspective that forestry training and rural pragmatism actually provide—was foreclosed before it could be evaluated on its merits. The organization lost access to a perspective it claimed to value (diversity of thought, background, experience) through the same social mechanism it used to enforce conformity (public dismissal of people who don't match the dominant culture). It's the Essay 1 "culture fit" problem expressed through the medium of feedback: the culture defines what counts as credible, and the feedback system enforces that definition in real time.

Accountability Versus Surveillance

These are different concepts, and organizations that confuse them pay a price that doesn't show up on the balance sheet.

Accountability creates focus. It establishes clear expectations, provides resources to meet them, and evaluates outcomes with enough context to distinguish between individual failure and systemic obstacles. Accountability asks: did we set this person up to succeed, and did they succeed? If not, what needs to change—the person, the support, or the expectation?

Surveillance creates anxiety. It monitors behavior rather than outcomes. It treats visibility as evidence of engagement and invisibility as evidence of disengagement. It assumes that people will only perform adequately when they know they're being watched, and it designs systems to ensure they're always being watched. Surveillance asks: is this person performing in ways that look correct? It doesn't care whether the performance produces results. It cares whether the performance is visible.

Under surveillance conditions, people optimize for visibility over impact. They choose projects that will be seen over projects that need doing. They communicate in channels where activity is monitored rather than channels where collaboration would be most effective. They schedule meetings to demonstrate engagement rather than to accomplish work. The organization gets a theater of productivity that looks impressive in status reports and evaporates on contact with actual outcomes. The people doing the real work—the quiet contributors who produce value in focused, independent conditions—become invisible, which under surveillance logic makes them suspect.

The digital tools that became standard in corporate environments over the past decade have made surveillance trivially easy to implement and nearly impossible to opt out of. Teams messages, Slack channels, project management dashboards, real-time status indicators—every platform designed for collaboration also functions as a monitoring system. When feedback is delivered in these public channels, it acquires a permanence that verbal corrections never had. A critique in a Teams chat is searchable, scrollable, and permanent. It exists in the archive long after the work has been corrected, available to anyone who wants to revisit your moment of visible failure.

This digital permanence changes the calculus of risk for everyone on the team. In a meeting, a public correction is uncomfortable but ephemeral—people remember the tone, but the specific words fade. In a chat channel, the correction is preserved verbatim. The shame of the moment is encoded into the team's permanent record. For neurodivergent employees—particularly those with ADHD, where Rejection Sensitive Dysphoria can be triggered by re-encountering past criticism—this archive becomes a minefield. Every scroll through a project channel carries the risk of stumbling across a moment of professional humiliation that reactivates the original shame response.

When everything is documented publicly, people stop asking questions. They stop acknowledging confusion. They stop admitting uncertainty. Because each of those normal, healthy, necessary professional behaviors—the behaviors that drive learning and collaboration and innovation—has been made permanently visible in a system that treats visibility as vulnerability. The team becomes a group of people performing confidence they don't feel, knowledge they haven't fully acquired, and alignment they haven't genuinely reached. The documentation system captures a fiction of competence and consensus. The actual competence and consensus deteriorate underneath it.

The Team Variability Problem

One of the most important things I observed at PPG was that this dysfunction wasn't universal. It was concentrated.

Other teams within IT—aerospace, logistics, data and analytics—seemed to function well. People in those groups spoke about their managers with respect. Collaboration appeared genuine rather than performed. The feedback I heard about those teams, both directly and through the informal channels I described in Essay 9, suggested that psychological safety varied dramatically depending on which team you were on and, more specifically, who was leading it.

This matters for a specific reason: it proves the dysfunction wasn't inevitable. It wasn't an unavoidable consequence of PPG's size, industry, or organizational structure. It was a leadership problem localized in specific teams. The same company, the same HR policies, the same corporate values statement—and radically different experiences depending on which manager you reported to. Some teams were functional because their leaders created conditions for psychological safety. Other teams—including mine in GCSS—were dysfunctional because their leaders created conditions for surveillance and public correction.

This team variability is important because it undermines the defense that organizational culture is an abstraction beyond any individual's control. Culture is what leaders do. When some teams thrive and others deteriorate under the same corporate umbrella, the variable isn't the umbrella—it's the leadership underneath it. The functional teams demonstrate what's possible. The dysfunctional ones demonstrate what happens when that possibility isn't realized.

The organizational response to this variability is revealing. When specific teams underperform or generate complaints, the typical corporate diagnosis focuses on the individuals within the team—their skills, their engagement, their "fit." Rarely does the diagnosis focus on the leader whose feedback practices, communication style, and management approach created the conditions for dysfunction. The assumption is that teams fail because of the people on them. The evidence suggests teams fail because of the people leading them. But holding leaders accountable for the quality of their feedback culture would require examining leadership itself, which is exactly the kind of upward accountability that the organizations I've described systematically avoid.

It also means that the Computerworld ranking decline—from #18 to #38—isn't measuring a company-wide cultural failure. It's measuring the aggregate effect of localized dysfunction severe enough to drag the overall score down despite the functional teams doing their best to compensate. The ranking doesn't identify which teams are the problem. It just confirms that enough employees are experiencing the kind of feedback culture I'm describing to move a national metric by twenty positions in a single year.

What Healthy Feedback Requires

Amy Edmondson's research is clear: teams perform better when members feel safe to take risks, ask questions, and acknowledge mistakes without fear of humiliation. This isn't soft management philosophy. It's empirical finding, replicated across industries, contexts, and cultures. Psychological safety predicts team performance more reliably than individual talent, resource allocation, or strategic clarity. Teams where people feel safe to be wrong outperform teams where people feel compelled to appear right.

MIT research goes further: public shaming is a reliable predictor of organizational dysfunction. Not an occasional byproduct that can be managed. A predictor. When public correction becomes normalized—when the team stand-up routinely includes moments of visible criticism—the downstream effects are measurable: reduced innovation, increased turnover, declining engagement, and the gradual replacement of honest collaboration with performative alignment.

Effective feedback has identifiable characteristics. It's specific—addressing a particular behavior or output rather than a generalized judgment of competence. It's actionable—providing clear direction about what to change rather than simply identifying what's wrong. It's timely—delivered close enough to the event to be useful rather than accumulated and deployed as an inventory of past failures. And it preserves dignity—separating behavior from identity, addressing what someone did rather than who someone is.

None of this requires extraordinary management skill. It requires ordinary management discipline: the decision to deliver criticism privately, to focus on work rather than workers, to treat feedback as a development tool rather than a power display. The fact that some teams at PPG achieved this while others didn't isn't a resource problem. It's a leadership choice problem. And when organizations don't hold leaders accountable for the quality of their feedback culture, they're making their own choice: that the comfort of managers who prefer public correction matters more than the performance of teams who would thrive without it.

The cost of that choice is invisible to the leaders making it, which is part of why it persists. A manager who publicly corrects an employee in a meeting doesn't see the downstream effects—the hours spent managing shame rather than doing work, the ideas never proposed because the risk of public failure outweighs the potential value, the quiet job search that starts after one too many moments of visible humiliation. They see a team that looks compliant and interpret compliance as success. The erosion happens beneath the surface, in the gap between what people produce and what they could have produced in a safer environment.

Susan Cain's research adds another dimension: introverts—and many neurodivergent people—need private processing time to integrate feedback effectively. Public feedback forecloses this by requiring immediate social management alongside cognitive processing. You can't thoughtfully consider how to improve your work when you're simultaneously managing shame, reading the room for social fallout, and performing composure for the benefit of your audience. The feedback doesn't land as information. It lands as threat. And the response to threat isn't learning. It's self-protection.

The Long Tail of Hostile Feedback

The effects of sustained exposure to public criticism don't end when the meeting ends. They accumulate into patterns of behavior that persist long after the specific incidents fade from memory.

Hypervigilance becomes the default. You enter every meeting scanning for signals of impending criticism. You draft every message calculating how it might be used against you. You avoid taking positions because positions create targets. Risk aversion replaces initiative, not because you've lost the ability to take risks but because the environment has taught you that risks carry consequences disproportionate to their benefits.

Trust in leadership erodes permanently. Once you've been publicly corrected by a manager—once you've experienced the specific vulnerability of having your competence questioned in front of peers—the relationship with that manager changes at a level that no subsequent kindness fully repairs. You might continue to work effectively with them. You might even maintain a professional relationship that looks functional from the outside. But the trust that enables genuine collaboration, honest communication, and shared risk-taking has been damaged. What replaces it is a transactional calculation: what does this person need from me, and how do I deliver it with minimum exposure?

This is the distinction between compliance and commitment that management literature endlessly discusses but rarely traces to its root cause. Leaders who manage through public correction get compliance. They get people who deliver what's asked, on time, to specification. What they don't get is discretionary effort—the extra thinking, the unrequested improvement, the "I noticed something that could be better and took initiative to fix it" that distinguishes high-performing teams from adequate ones. Discretionary effort requires trust. Trust requires safety. Safety requires knowing that taking a risk won't result in public humiliation if the risk doesn't pay off. Hostile feedback environments eliminate discretionary effort by making it irrational to offer.

And the behavioral shifts aren't limited to the person who was publicly criticized. They ripple through the team. Every person who witnessed the correction learned something about the environment they work in. They learned that visibility carries risk. They learned that mistakes will be displayed. They learned that the safest strategy is to produce work that is adequate and invisible rather than ambitious and exposed. The team's collective intelligence contracts—not because the individuals became less capable, but because the environment made capability dangerous.

When organizations eventually measure the result—through engagement surveys, turnover data, or external rankings like Computerworld—they're measuring the accumulated effect of thousands of these moments. Twenty positions on a ranking don't disappear because of a single bad meeting. They disappear because a pattern of hostile feedback, sustained over years, teaches enough employees to stop bringing their best thinking, their honest questions, and their genuine engagement to work. What remains looks like performance. It's compliance.

The people who raised concerns about this dynamic—who tried to name what was happening, who pushed back on public correction, who asked for feedback practices that preserved dignity—were the early warning system the organization needed. Terminating them, or silencing them until they left voluntarily, didn't solve the problem. It removed the diagnosticians. The disease continued, invisible to the leadership that had eliminated the people who could see it, until an anonymous survey measured what everyone on those teams already knew.

Feedback designed to develop people looks like partnership. Feedback designed to control people looks like performance. The difference isn't subtle, and the consequences aren't minor. When you build a system that treats public correction as accountability, you don't get accountable teams. You get silent ones. And silent teams, as I described in Essay 9, don't stop having problems. They stop telling you about them.

← Essay 9: Staying Silent Essay 11: Severance Under Duress →