You probably don’t need a definition. If you’ve worked in a toxic environment, you felt it before you could name it—the low-grade dread on Sunday evenings, the careful way you chose your words in meetings—if you spoke at all—the growing suspicion that the rules applied differently depending on who you were. The classic version has recognizable villains: the boss who humiliates, the colleague who undermines, the culture that runs on fear. And yes—the engagement survey that gets conducted annually and referenced never.

So yes—the screaming boss is a problem. The workplace that runs on fear is a problem. The organization that treats certain people as invisible is a problem.

But there’s another version of toxic that doesn’t make it into those categories. It has no villain. No incident report. No single moment anyone can point to. It’s the kind of toxic that employees feel in their bones but struggle to describe at the dinner table, because describing it sounds almost reasonable. “My organization doesn’t have clear role definitions.” “We say we value people, but the culture doesn’t reflect that.” “Nobody knows what the rules actually are until they break one.”

That’s structural toxicity—and it may be the most widespread kind that goes unexamined.

The Kind That Isn’t Anyone’s Fault (But Still Needs Fixing)

Here’s the thing about structural toxicity: most of it isn’t intentional. It isn’t the product of malicious planning in a boardroom. It’s the accumulated result of neglect, underdeveloped leadership, poor organizational design, and a very human tendency to assume that if nobody is complaining loudly, things must be fine.

The absence of intent, however, does not reduce the harm. And it does not reduce the organization’s responsibility to address it.

I want to explore two distinct mechanisms through which workplaces become structurally toxic—not through bad behavior, but through bad architecture. The first involves what organizations claim to be. The second involves what organizations fail to build.

Mechanism One: Integrity Failures—The Gap Between What’s Posted and What’s Practiced

1. Values on the Wall, Not in the Room

Nearly every organization has a values statement. Respect. Integrity. People First. Innovation. They appear on websites, in onboarding packets, and sometimes—if the design budget stretched far enough—on an inspirational wall in the lobby.

MIT Sloan’s research noted something quietly devastating about this. Their analysis identified five cultural attributes that employees most associate with a poisoned workplace: disrespect, exclusion, unethical behavior, cutthroat competition, and abuse. These are not what organizations claim to value—they are what organizations fail to prevent. And here’s the irony: integrity was the most frequently listed core value among the companies studied. Collaboration ranked second. Respect came fourth. Organizations are, in other words, publicly committed to the very opposites of what their employees are actually experiencing. When that gap is wide enough, employees don’t experience it as a policy failure—they experience it as a betrayal.

That’s not a small distinction. A betrayal doesn’t just disappoint. It erodes trust in everything else the organization says. When the stated values and the daily lived reality diverge, employees learn quickly which one to actually believe. The lesson doesn’t take long to learn. And then they respond accordingly—which usually means keeping their heads down, investing less, and updating their résumés.

The toxicity here isn’t any one behavior. It’s the institutional dishonesty of promising something and delivering its opposite, repeatedly, without ever acknowledging the gap.

2. Results-at-Any-Cost, Disguised as High Standards

This one wears the most convincing costume. “We have high expectations here.” “We push people to be their best.” “This isn’t a place for people who aren’t committed.”

There is a legitimate version of all of those statements. Organizations that genuinely invest in their people, set clear goals, and hold everyone to consistent standards can ask a lot without becoming toxic. The difference lies in what stops mattering when the pressure is on.

When excessive workloads are framed as commitment, when chronic overwork is treated as evidence of dedication rather than a design failure, when the answer to “I’m overwhelmed” is “we all are”—that’s not a high-performance culture. That’s a high-performance narrative layered over a dysfunctional reality.

The American Institute of Stress points to something particularly ironic here: resilience training as a response to burnout often treats the symptom while protecting the cause. Resilient employees, the research suggests, are more likely to leave—because they’re better equipped to recognize an unfixable situation and do something about it.

3. Inconsistent Rule Enforcement

Few things communicate the actual power structure of an organization more clearly than watching who the rules apply to.

The formal org chart says one thing. The enforcement pattern says another. When standards shift depending on who’s involved—when the same behavior earns consequences for one employee and a knowing shrug for another—employees aren’t confused. They’re paying attention. They are learning, very precisely, where power actually lives in this organization and what it protects.

Inconsistent enforcement doesn’t just feel unfair. It creates a culture where the written rules become largely decorative and the unwritten ones—which usually favor whoever is most senior, most connected, or most capable of generating short-term results—are the ones that actually govern. The damage is cumulative and quiet. Nobody files a report about “I noticed that the policy was applied differently to two people.” But everyone notices.

Mechanism Two: Design Failures—What Organizations Never Built in the First Place

4. Unclear or Shifting Roles and Expectations

Here’s an organizational problem so familiar that most organizations have simply accepted it: nobody is entirely sure what they’re actually supposed to be doing, or the answer changes regularly enough that certainty feels pointless.

This isn’t a new discovery. Research by Robert Kahn and colleagues in 1964—surveying over 200 organizations—identified role ambiguity and conflict as key sources of occupational stress, with clear correlations to psychological strain. That finding is now sixty years old. It has been replicated many times since. And yet role ambiguity remains one of the most persistent features of organizational life, particularly in public sector and multi-stakeholder environments where job boundaries tend to be porous, priorities arrive from multiple directions, and the person who set the expectations last quarter may have been reorganized into a different role.

The consequences are predictable and compounding. When employees don’t know what success looks like, they can’t achieve it—but they’ll be held accountable as though they could. When priorities shift without explanation, the rational response is to stop investing deeply in any of them. The organization accepted the ambiguity. The employee doesn’t get to accept it. They just have to live inside it.

Nobody designed this to cause harm. That’s precisely what makes it so durable.

5. Communication Dysfunction

Information in a healthy organization flows in multiple directions. Decisions get explained. Feedback gets offered and received. People understand not just what they’re being asked to do, but why.

In organizations where communication has failed as a system—not because anyone is being secretive, but because the infrastructure for it was never built—employees operate in a persistent state of uncertainty. They don’t know if their work is valued. They don’t know what leadership is thinking. They don’t know whether the silence after they raised a concern means it was handled, ignored—or whether the act of raising it has made them the subject of a different kind of scrutiny entirely.

That uncertainty isn’t neutral. The American Institute of Stress notes that unclear goals and vague expectations are direct contributors to burnout—not because people can’t handle challenge, but because the brain has a particular intolerance for ambiguity in high-stakes situations. When employees can’t read their environment, they spend cognitive energy scanning for signals instead of doing their actual work. Over time, that’s exhausting in ways that don’t show up in any performance report.

Communication dysfunction is easy to mistake for a culture problem or a personality mismatch. It’s often neither. It’s a system that was either never designed or never developed to carry the information employees need to function well.

6. No Meaningful Feedback or Development Pathways

Most organizations will tell you they invest in their people. What this sometimes means in practice is that they have a performance review process, which is not the same thing.

A review that happens once a year, evaluates the past rather than building toward the future, and delivers vague assessments against vague criteria is not a development system. It’s a documentation system. It protects the organization in the event of a termination dispute. It does relatively little for the person sitting across the table.

The MIT Sloan research identified something striking about development opportunities: lateral career moves were 2.5 times more powerful than compensation in predicting whether an employee stayed. Twelve times more powerful than a promotion. What employees want, it turns out, is not just more money or a better title. They want to grow, to learn, to feel that the organization has an interest in their trajectory. When that’s absent—when people look ahead and see no path, no investment, no signal that the organization is thinking about their development—they make a reasonable calculation: this organization is not going to give me what I need to become who I’m trying to become. And then they leave, or they stay and stop growing, which is worse for everyone.

Sometimes the barrier isn’t a policy—it’s the gauntlet of approvals required to access development at all. When requesting investment in someone’s growth means navigating a chain of forms, justifications, and sign-offs exhausting enough to discourage the attempt, the message received is functionally identical to a refusal. Most people eventually stop asking. The organization interprets the silence as satisfaction.

That pattern—the gap between what organizations say they value and what the structure actually supports—runs through all six of these mechanisms. And in every case, the people who feel it most acutely are the ones with the least power to fix it.

Worth Questioning

The engagement survey that gets conducted annually and referenced never is not a minor administrative failure. It’s a structural choice—and structural choices, made repeatedly and without accountability, are exactly how workplaces become toxic without anyone trying.

The through-line connecting all six of these is the same: none of them require a bad actor to create, but all of them require someone willing to see them clearly—and fix them.

That’s the uncomfortable part of structural toxicity. It doesn’t resolve itself. It doesn’t improve because people try harder or develop more resilience. It persists because the organizations experiencing it either can’t see it—because it looks normal, because it’s always been this way—or see it and treat it as someone else’s problem to solve.

The employees living inside these structures are not imagining it. What they’re feeling is real, it is documented, and it does have a name.

Employees in structurally toxic environments rarely make noise about it—they simply stop investing, stop speaking up, and eventually stop showing up. That silence is easy to mistake for satisfaction.

The question is whether the people with the authority to address it are willing to stop mistaking the absence of drama for the presence of health.

Can We Think Different?

On integrity failures:

When your organization’s stated values and its daily culture diverge—who knows? Is that gap acknowledged anywhere, by anyone in a position to close it? Or does the organization keep posting the values and hoping nobody does the math?

If a new employee watched how decisions get made here for 90 days, what would they conclude your organization actually values?

On design failures:

If you asked five people in your organization to describe their role and its boundaries, how many different answers would you get? What does that tell you?

When someone raises a concern, proposes an idea, or asks for feedback—what actually happens next? Is there a system for that, or is the outcome determined entirely by who they happened to ask?

Can the people in your organization see a future for themselves here? Not a promotion—a direction. If they can’t, whose responsibility is that?

When did your organization last invest—in time, money, or attention—in someone’s growth without an immediate operational return? What does the answer tell you?

---