Back to Thoughts
May 19, 2026

What Company Culture Actually Is

There’s a version of “company culture” that shows up in job postings and employer branding decks, and then there’s the real version. The one that determines whether people spend their energy on the work or on navigating each other.

A lot of companies treat culture like it’s the fun stuff. Ping pong tables, happy hours, team-building retreats. Those things are fine. They can make a workplace more enjoyable. But without the right foundation underneath them, they’re decorations on a building with no structure. You can have the best snack bar in the industry and still be a place where nothing gets done without kissing the right person’s ring first.

What It Looks Like When It Works

I’ve been in environments where culture actually worked. Not because anyone was particularly focused on culture as a concept, but because the basics were in place. The mission was clear. People understood how their work connected to it. There was enough transparency that you could make decisions without having to guess what leadership actually wanted.

I’ve written before about what happened at Texas A&M, where a handful of technologists across departments pushed for changes that reshaped how the university ran its infrastructure. None of it was anyone’s job. It worked because the culture let it work.

That’s what healthy culture looks like in practice. Not a set of values on a wall. Just an environment where people can focus on the actual work instead of spending half their energy figuring out who to avoid, who to flatter, and whose feelings to protect before they can get something done.

What It Looks Like When It Doesn’t

A broken culture is easy to recognize once you’ve been in it. It’s an environment where the org chart says one thing but the actual power structure is something completely different. Where getting a decision made has less to do with the merit of the idea and more to do with whose name is attached to it.

The examples are everywhere. Sellers throwing fits to get projects prioritized because their commission depends on it. People spending weeks building political cover for decisions that should take an afternoon. Teams learning not to bring problems to leadership unless they’ve pre-sold the solution to everyone who might feel threatened by it. The problems that get surfaced are the ones that are safe to talk about, not necessarily the ones that matter most.

All of that is energy. Real, finite, human energy that’s being spent on politics instead of outcomes. And the people burning that energy know exactly what they’re doing. They’re not confused about priorities. They’ve correctly identified that in their environment, managing relationships is more important than doing good work.

The Cost

The real cost of a political culture is everything that doesn’t happen. The engineer who saw a production problem forming but didn’t raise it because the last person who raised one got labeled as difficult. The project that everyone knows is failing but nobody will say out loud because the VP who sponsored it is untouchable. The senior developer who leaves not because they got a better offer, but because they got tired of spending more time managing personalities than writing code.

The underlying problem is that keeping the existing structure intact becomes more important than whether the structure is producing the right results. And the people at the top either don’t realize it’s happening because the uncomfortable information stopped reaching them a long time ago, or they do realize it and just don’t want to hear it.

In my experience, a lot of it traces back to leadership egos. The mission gets clouded because someone at the top is more interested in being right than in getting the right outcome. The transparency disappears because admitting something isn’t working feels like a personal failure. The hierarchy calcifies because it protects the people who built it. Sometimes it’s about control. Sometimes it’s about making sure nobody gets close enough to see just how bad things actually are.

What It Actually Takes

The foundation of a good culture isn’t complicated. It’s a clearly defined mission that people can understand and believe in. It’s leaders who are actually there to lead, not to protect their own position. It’s making sure every team and role can draw a line between what they do and why it matters. It’s transparency about what’s going on, what’s working, and what isn’t. And it’s giving people room to solve problems through first principles instead of through hierarchy.

When the foundation is missing, no amount of happy hours will fill the gap. You’ll have a nice time at the bar and then go back to the same broken environment on Monday, spending the first half of the week figuring out the politics and the second half trying to get actual work done in whatever time is left.

Culture isn’t really about organizational design. It’s about whether people can spend their time on the customer, the product, and the problems in front of them, or whether they’re spending it figuring out whose ego to manage before they can get anything done. We all want to feel like we’re contributing to something that matters. The job of leadership is to make that possible, not to build a system where the only way to survive is to play the game.