Jon's Job Blog

My manager canceled our one-on-one three times in a row. No explanation, no reschedule, just the calendar notification disappearing from my week like a conversation the organization had decided not to have. When I finally asked about it—carefully, the way you learn to ask things in corporate environments, packaging concern as curiosity—I got a vague response that communicated nothing except that the question itself was unwelcome.

That was the moment I started self-editing. Not the first time I'd held something back at work. But the first time I consciously registered the calculation: the cost of asking exceeds the cost of not knowing. From that point forward, I didn't bring my actual thinking to work. I brought a curated version—trimmed of anything that might cause friction, emptied of the observations that might have helped if anyone had wanted to hear them.

This essay is about the machinery of that silence. Not the dramatic kind—not whistleblowing or open dissent. The quiet, daily, corrosive kind. The kind where you know something is wrong and you've learned, through accumulated evidence, that saying so will cost more than staying quiet. The kind that organizations engineer through consequences and then mistake for consent.

The Architecture of Quiet

Every organization I've worked in had an open-door policy. The phrase appeared in onboarding materials, employee handbooks, town hall presentations. Managers said it in introductory meetings. "My door is always open." The implication was that honesty was not just tolerated but invited—that the organization wanted to hear what employees actually thought.

In practice, the door was open for certain kinds of feedback. Aligned suggestions—the kind that reinforced existing strategy with minor variations. Easy problems—the kind with clear solutions that didn't implicate anyone above you. Positive observations—the kind that confirmed leadership was doing a good job. These passed through the open door without friction. They were the feedback the organization was actually soliciting when it said it wanted feedback.

What didn't pass through: concerns that implicated power. Observations about process failures that traced back to management decisions. Questions about why resources were allocated one way and not another. Feedback that required the listener to consider whether they, or their peers, or the system they'd built, might be part of the problem. This feedback hit the open door and bounced. Sometimes quietly—the concern raised in a meeting that received a nod and no follow-up. Sometimes loudly—the suggestion reframed as "not being a team player" or "not understanding the bigger picture."

The result was a filtration system that looked like openness and functioned as suppression. Employees learned, through trial and correction, which observations were welcome and which triggered consequences. The learning wasn't explicit. Nobody posted a sign saying "don't raise concerns about management." It happened through the accumulation of small signals: the meeting where your concern was met with visible irritation. The one-on-one that got canceled after you pushed back on a decision. The peer who raised a similar issue and found themselves on a performance improvement plan two months later. You watched. You learned. You adjusted.

Amy Edmondson's research on psychological safety documents this dynamic with precision. In environments where speaking up carries perceived risk, people don't stop having concerns. They stop voicing them. The problems don't disappear. They go underground—invisible to leadership, metastasizing in the spaces between what people know and what they're willing to say. Leadership, operating on incomplete information, makes decisions that would have been different if the information had been flowing. But the information stopped flowing because leadership made it unsafe to flow.

The learning curve is steep and permanent. You might test the boundary once or twice early in your tenure—raise a concern, push back on a decision, ask a question that implies someone above you made an error. If those tests are met with engagement, trust builds. If they're met with consequences—however subtle—the lesson calculates instantly. You don't need to be fired for speaking up. You just need to see someone else's concern evaporate into a silence that everyone in the room understands. The learning is observational, collective, and remarkably efficient. One unanswered concern teaches an entire team what not to say.

It's a closed loop. Create consequences for speaking up. Watch people stop speaking up. Interpret the silence as evidence that everything is fine. Make decisions based on that false evidence. Create more problems. Wonder why no one flagged the problems earlier.

The Cognitive Tax of Self-Censorship

Silence isn't passive. It's work. Constant, draining, cognitive work that operates beneath the surface of every professional interaction.

When you suppress a concern, it doesn't vanish. It becomes a puzzle you solve alone. Every question you withhold becomes a solo contingency plan. Work that should have been distributed across a team—surfaced in a meeting, debated, refined through collective thinking—instead gets shouldered by the individual who saw the issue but learned not to raise it. You end up doing two jobs simultaneously: the work you're paid for, and the invisible work of managing the information the organization has made it unsafe to share.

The dissonance is the hardest part. You know something. You see a process that's failing, a decision that doesn't make sense, a pattern that's going to cause problems downstream. You can't say it. So you hold two realities in your head at once: what you know to be true and what you're performing as true. Chronic suppression creates an internal conflict between perception and expression that doesn't resolve. It just sits there, generating anxiety, consuming the cognitive bandwidth that should be going toward the work itself.

For someone with ADHD—where managing attention and emotional regulation already consume significant resources—the additional load of constant self-censorship is devastating. As I described in Essay 8, masking neurodivergence is already a second job. Layering professional silence on top of cognitive masking means you're running three parallel processes at all times: the actual work, the neurotypical performance, and the emotional suppression. The idea that people operating under this load should also be delivering their best creative and analytical work is a fantasy that organizations maintain because acknowledging the cost would require changing the environment.

Harvard research on psychological safety confirms what this feels like from the inside. Workers unable to speak up experience higher rates of stress, burnout, and turnover. But the organizational cost is equally severe: low psychological safety means missing critical information about operational problems, customer concerns, and process failures. The information doesn't cease to exist because people stop sharing it. It just stops reaching the people who could act on it, until it surfaces as a crisis rather than a concern.

There's a particular cruelty to how this dynamic intersects with performance evaluation. When you're solving problems alone that should have been solved collaboratively—because raising them would mark you as difficult—the work takes longer, the solutions are less robust, and the effort is invisible. You hit the deadline, but the path to hitting it consumed twice the energy it should have because you couldn't access the team's collective intelligence without first navigating the team's collective silence. Your performance review reflects the output. It doesn't capture the cost. And over time, the cost accumulates in ways that look, to managers operating without full information, like declining capability rather than unsustainable working conditions.

The Professionalism of Dishonesty

"Be honest but not uncomfortable. Raise concerns without seeming negative. Challenge decisions without creating conflict." These are the contradictions that professionalism demands, and they amount to a request for dishonesty dressed in the language of emotional intelligence.

Professionalism, as practiced in most corporate environments, is a code for emotional suppression. Maintain composure regardless of circumstances. Project confidence you don't feel. Express understanding toward decisions you disagree with. Perform engagement in meetings that waste your time. The professional mask isn't optional—it's the baseline requirement for being taken seriously, and it requires sustained emotional labor that compounds every other form of workplace exhaustion.

What makes this particularly corrosive is that it operates under the banner of honesty. Organizations say they want candor. They say they want "constructive feedback." They say they value "diverse perspectives." But the operational definition of each is narrow enough to exclude anything genuinely challenging. Constructive feedback means feedback that doesn't require the listener to change. Diverse perspectives means perspectives that arrive at the same conclusion through a different demographic lens. Candor means honesty that confirms rather than disrupts.

Brené Brown's research on organizational vulnerability makes the consequence clear: organizations that punish honesty in the name of morale don't build morale. They build resentment and disengagement. Employees who can't express concerns don't stop having them. They stop bringing them to the workplace. The concerns migrate—into private conversations with trusted colleagues, into anonymous Glassdoor reviews, into quiet job searches. The organization loses access to the information while the information continues to exist, circulating in channels leadership can't monitor and increasingly can't influence.

I experienced this migration firsthand. By mid-2023, I'd stopped raising substantive concerns in formal channels. Not because the concerns had diminished—they'd grown. But because every attempt to surface them had been met with some version of deflection: the concern acknowledged but not acted on, the meeting scheduled but not followed through, the promise made and quietly abandoned. I learned the lesson the environment was teaching. My concerns didn't stop existing. They just stopped reaching the people who could have addressed them.

The migration creates a two-tier information system within organizations. The official channels—meetings, one-on-ones, feedback surveys, town halls—carry the sanitized version. The real information travels through unofficial channels: the conversation in the parking lot after a meeting, the Slack DM between trusted colleagues, the lunch where everyone says what they couldn't say in the room. Leadership has access to the official channels. They rarely have access to the unofficial ones. So they operate on a version of reality that has been filtered, softened, and depleted of the information they'd need most to make good decisions. They govern a country whose actual conditions they've never visited.

When Personal Crisis Meets Professional Silence

Spring and summer of 2023 were the period when the weight of professional silence became hardest to carry—not because I was hiding everything, but because what I could talk about and what I couldn't occupied different registers of the same exhaustion.

I was going through a divorce, and I was open about that with my team. My manager at the time was supportive in the ways that matter on a personal level—she recommended a divorce attorney, checked in on how I was doing, showed the kind of human decency that individual relationships can provide even inside dysfunctional systems. I ended up going with an attorney closer to home, but the gesture was genuine. I wasn't masking the personal crisis. The people around me knew what I was going through.

What I was masking was everything else. The professional concerns—the process failures I'd observed, the management dysfunction I couldn't name without implicating people above me, the growing sense that the organization's stated values and its operational reality were diverging in ways that would eventually become visible. Those concerns remained suppressed even as my personal life was an open book. The paradox was disorienting: I could tell my team I was getting divorced, but I couldn't tell them that I thought our department's communication practices were failing, or that the feedback I'd tried to raise had been systematically deflected.

The corporate wellness rhetoric says "bring your whole self to work." The operational reality is that certain parts of your whole self are welcome—the parts that demonstrate vulnerability in approved ways, that inspire colleagues, that can be featured in an ERN presentation. Personal struggles that generate sympathy are acceptable. Professional observations that generate discomfort are not. The boundary between what you're allowed to share and what you're expected to suppress isn't drawn around honesty. It's drawn around convenience.

So I occupied a strange middle ground: personally transparent and professionally silent. Open about the hardest thing in my personal life, closed about the concerns that were eroding my professional engagement. The people around me could see the divorce. They couldn't see the accumulating frustration of working inside a system that had taught me, through repeated experience, that raising concerns about the system itself would cost more than staying quiet.

The cognitive cost of maintaining that split—genuine about one form of struggle, performative about another—was its own kind of exhaustion. It wasn't the total masking I described in Essay 8, where everything is hidden. It was a selective honesty that required constant calibration: this I can say, this I can't, this topic is safe, this one triggers consequences. The calculation never turned off. Even in moments of genuine personal support from colleagues, I was simultaneously running the assessment of which professional observations to continue withholding.

When I did reach out for additional support—through the EAP, through conversations about workload—the response was less personal and more institutional. The EAP offered a limited number of sessions with a counselor unfamiliar with workplace dynamics. The workload conversation produced the "eat more vegetables" advice I described in Essay 8. The organization could accommodate personal vulnerability in the abstract. It couldn't accommodate the specific observation that its own practices were contributing to the problem.

The three-month wait for therapy during that crisis period was its own form of institutional silence. When the system designed to help can't see you for twelve weeks, and the workplace expects uninterrupted performance in the meantime, you learn something fundamental about how much the organization's stated care actually extends. The personal support from individual colleagues was real. The institutional support was a brochure.

The Feedback Loop That Destroys Organizations

Here is the mechanism that should concern every executive, board member, and investor reading this: when you create an environment where speaking up has consequences, people stop speaking up. When people stop speaking up, problems stop appearing in feedback. When problems stop appearing in feedback, leadership interprets the quiet as alignment. When leadership interprets quiet as alignment, they continue—and often accelerate—the decisions causing the problems. The problems compound underground until they surface as crises that cost exponentially more than they would have cost to address when someone first tried to raise them.

This isn't theoretical. PPG's Computerworld "Best Places to Work in IT" ranking dropped from #18 in 2025 to #38 in 2026—a 20-position decline in a single year. That ranking is based on employee surveys. The problems I was raising internally in 2023 and early 2024, the concerns that were met with canceled one-on-ones and vague responses, didn't disappear when I was terminated. They stopped showing in individual feedback and started showing in aggregate metrics that the organization couldn't dismiss as one disgruntled employee.

That's the 15-month lag between silenced concerns and measurable consequences. The concerns I raised were accurate. The organization's response was to remove the person raising them rather than address the conditions being described. And 15 months later, a survey of the remaining employees confirmed that the conditions were real, widespread, and getting worse.

The irony is structural. Organizations silence dissent to protect morale and maintain alignment. The silencing creates an information vacuum. The vacuum allows problems to compound. The compounded problems eventually surface in metrics the organization can't control—employee surveys, retention rates, ranking drops, Glassdoor reviews. By then, the cost of addressing the problems has multiplied, and the people who could have helped solve them early have been terminated, transferred, or have left voluntarily.

PPG's response to its declining performance during this period was instructive. Rather than examining the cultural conditions that were driving employee dissatisfaction—the conditions people like me had tried to flag—the organization pursued restructuring. In Q4 2024, PPG recorded $314 million in restructuring charges and eliminated approximately 1,800 positions. The assumption embedded in that decision is revealing: the problem is structural cost, not structural culture. Remove the people, keep the system, expect better results.

But the 20-position Computerworld decline happened after the restructuring, not before. The people were removed. The silence deepened. And the remaining employees—the ones who watched their colleagues get eliminated and drew the obvious conclusion about what happens to people who make the organization uncomfortable—told a survey what they would never tell their managers. The restructuring didn't fix the culture. It confirmed the culture's thesis: that people are costs to be managed, not voices to be heard.

This is the organizational cost of silence, and it's invisible to every accounting system. It doesn't appear on the income statement. It doesn't trigger goodwill impairment. It doesn't factor into the restructuring charge analysis. It just sits there, eroding capability, until the erosion becomes visible enough that someone—usually an external survey—measures it.

What Speaking Would Have Required

I want to be clear about what would have been necessary for me to speak up. Not courage. Courage was never the issue. The issue was rational risk assessment. In an environment where raising concerns led to canceled meetings, vague responses, and the observation that other people who pushed back found themselves on the wrong side of performance reviews, silence wasn't cowardice. It was calculation.

This distinction matters because the resilience narrative—which I'll examine more closely in Essay 14—frames silence as a personal failure. If you didn't speak up, you weren't brave enough. If you didn't push back, you didn't care enough. This framing ignores the obvious: people with mortgages, families, and limited savings don't have the luxury of courage when the cost of speaking is their livelihood. The people most likely to stay silent aren't the least brave. They're the most exposed. They've done the math, and the math says the consequences of honesty exceed the consequences of suppression—at least in the short term. In the long term, both exact their costs.

What would have been required was an environment where the consequences of speaking up were different. Where a concern raised in a one-on-one was acknowledged, explored, and either acted on or explicitly explained. Where the person raising the concern didn't become the problem to be managed. Where leadership demonstrated, through repeated action rather than repeated rhetoric, that honesty was genuinely valued even when it was uncomfortable.

This is what psychological safety means in practice. Not the absence of conflict—conflict is inevitable in any organization doing meaningful work. But the presence of trust that conflict can be navigated without career consequences. That the person who says "I think this decision is wrong" will be engaged with rather than marginalized. That the reward for honesty is engagement rather than isolation.

I never found that at PPG. Not in the open-door policies. Not in the one-on-ones that were scheduled and then disappeared. Not in the feedback channels that filtered for comfort over accuracy. The infrastructure of openness existed. The practice of openness did not.

And the data suggests I wasn't alone in that experience. Twenty positions on a national ranking don't disappear because of one disgruntled employee. They disappear because a critical mass of employees—the ones still there, the ones who stayed and kept working after people like me were removed—told an anonymous survey what they couldn't safely tell their managers: something here is broken, and nobody's listening.

The Slow Poison

Silence doesn't kill organizations quickly. It's a slow poison that degrades capability incrementally, invisibly, until the degradation becomes acute enough to measure. By then, the institutional knowledge that could have diagnosed the problem has walked out the door—voluntarily or otherwise.

For individuals, the poison works differently but just as gradually. You start by holding back one concern. Then another. Then you stop preparing concerns to hold back because the act of formulating them only to suppress them is its own form of cognitive waste. You disengage from the work at a level that's invisible to performance metrics but devastating to the quality of your contribution. You become what the organization inadvertently optimized for: a person who shows up, performs adequately, and never makes anyone uncomfortable. A person whose most valuable thinking happens outside of work, if it happens at all.

The shame dimension makes this worse. Brené Brown distinguishes between guilt—"I made a mistake"—and shame—"I am a mistake." In environments where feedback is public and concerns are treated as problems, the experience of being silenced registers not as a communication failure but as a personal one. You internalize the message. Maybe I'm wrong. Maybe I don't understand the bigger picture. Maybe the problem is me. For someone with ADHD, where Rejection Sensitive Dysphoria already amplifies the emotional weight of criticism, this internalization happens faster and cuts deeper. Public correction doesn't just sting. It neurologically overwhelms. And the shame response—the conviction that you are the problem rather than the witness of a problem—becomes another reason to stay silent.

I spent the last year and a half of my time at PPG in this state. Not disengaged in the way HR metrics would capture. I hit deadlines. I attended meetings. I completed my automation work. But I'd stopped contributing the kind of thinking that had made me valuable in the first place—the pattern recognition, the systemic analysis, the willingness to say "this process is broken and here's how to fix it." That thinking was still happening. I just stopped sharing it because the environment had made sharing it more expensive than keeping it to myself.

After termination, I discovered something unexpected. The same analytical thinking that the organization had gradually taught me to suppress—the observations about culture, process, structure, the connections between decisions and consequences—that thinking became the foundation of this blog. The 22-essay series you're reading exists because I spent four and a half years accumulating observations that I couldn't voice inside the organization. The silence didn't destroy the thinking. It just delayed its expression until I found a context where honesty didn't carry career consequences.

That's the final irony. Organizations suppress employee voice to maintain control. But voice doesn't disappear when you silence it. It just finds other channels—Glassdoor reviews, LinkedIn posts, industry surveys, and occasionally, 22-part essay series written by people who tried to speak up inside the system and learned the hard way that the system wasn't listening.

Problems don't disappear when you stop hearing about them. They stop showing in feedback. And then they show up in metrics you can't control.

← Essay 8: Invisible Labor Essay 10: Hostile by Design →