Organizational Subcultures: The Hidden Structure of Company Culture

By Joe Newsum

Walk into any company and ask what the culture is like, and you will get one answer, as if culture were a single thing. It is not. The person in engineering experiences a completely different daily reality than the person in sales, who experiences something different again from the person in finance. They work for the same company, under the same stated values, and they are living in different worlds.

This is the truth that most culture conversations miss. Organizational subcultures are not a footnote to company culture. They are the actual structure of it. The company-level culture, the one printed on the wall, is mostly an abstraction. The culture people actually live in is the subculture of their team, their department, their function. That is where culture is real, and that is where it is either working or quietly failing.

Once you can see the structure of these subcultures, you can see why working across an organization so often feels like friction, why teams silo, and most importantly, what to do about it.

I spent years as an executive inside these battles, and I was not a neutral observer of them. I fought to defend and expand the functions I ran, and I was sure that was good leadership. I could not yet see that I was inside a subculture, behaving exactly the way it shaped me to. The frame on this page is the one I wish I had then. I am going to lay it out, and at a few points I will ask you to look at your own experience, because that is where it will actually land.

What an Organizational Subculture Actually Is

The real definition is simpler than the textbooks make it. Culture is the cumulative effect of how people think and behave. A subculture is that same thing inside a smaller group, a team, a department, a function, a discipline, that differs from the organization as a whole.

The common description of subcultures is too flattering. The textbooks say each function has its own language, its own rhythm, its own standards, its own way of working, as if every subculture were a coherent, well-formed culture in miniature. A few are. Most are not. Most subcultures are not designed at all. They are the accidental, accumulated residue of how a particular group of people happens to think and behave, with no shared language, no agreed standard, and no deliberate rhythm. What looks from the outside like a distinct culture is, on the inside, often closer to chaos: a group of individuals each operating from their own defaults, papering over the gaps with constant real-time translation.

That is the lived experience most people would recognize. The handoffs that never quite work. The same word meaning three different things to three different people. The meeting where everyone nods and then does something different. That is not a coherent subculture with its own clear standards. That is an accidental subculture, which is what almost every subculture is until someone makes it deliberate.

The functions and teams that genuinely feel coherent, where people share language and know what great looks like, did not get that way by accident. Someone built it. That is the entire point of this body of work: the difference between an accidental subculture and a deliberate one, and how to move from the first to the second.

Think about your own team. Is it a coherent subculture with shared language and standards that everyone could name, or is it a group of capable people each operating from their own defaults, translating across each other every day?

You Feel Subcultures Most Where You Belong Most

People do not experience all their subcultures equally. There is a gradient of belonging, and it is strongest closest in.

Your strongest sense of belonging is to your team, the people you are in the trenches with every day. It fades as the circle widens. The department is real but less immediate. The function is more of an identity than a daily experience. The company, for most people, is an abstraction, a logo and a set of values they could not recite. This is why a person will run through a wall for their team and feel almost nothing for a company initiative. The belonging lives close in. The evidence agrees: Gallup finds that managers account for at least 70% of the variance in employee engagement across business units. Engagement is not set by the company. It is set close in, at the level of the team and the person who runs it.

Here is the uncomfortable part. Strong belonging does not mean healthy culture. Your team can be the place you feel the most belonging and also be dysfunctional, conflict-avoidant, gossipy, mediocre, or quietly toxic. In fact the strength of the belonging often hides the dysfunction, because people mistake closeness for health. The tightest tribes can be the most dysfunctional ones, precisely because the bond makes the problems invisible from the inside. Belonging feels good. It is not the same as good.

The team you feel the most loyalty to, is it actually healthy, or is the loyalty making it hard to see what is not working?

The Hidden Structure: The Culture Matrix

Subcultures are not a random scatter. They organize in two directions at once, and seeing both directions is the key that unlocks everything. Picture a matrix. Down one side are the activities every group does, how they run meetings, give feedback, make decisions, communicate. Across the top are the functions, sales, engineering, finance, and the rest. Culture lives in the cells.

The matrix contains two different cultures depending on which way you read it, and this is the insight that almost every treatment of subcultures misses.

Read it vertically, down a single column, and you are looking at a functional culture. Everything about how engineering operates, top to bottom, how they run their meetings, give feedback, make decisions, plan their work. The column is the function’s own subculture, its distinct way of doing its work. Read the next column and you get a different functional culture entirely. Finance does not run meetings the way sales does. Engineering does not make decisions the way marketing does. Each column is its own world.

Read the matrix horizontally, across a single row, and you are looking at something else entirely: how the whole organization works together. The meetings row, read across every function, is the organization’s shared culture of how meetings happen. The decisions row is how decisions get made across the company. This horizontal culture is the connective tissue, the how-we-work-together layer that determines whether the functions can actually operate as one organization or only as a set of separate tribes.

Every cell belongs to both at once. A sales team meeting is shaped by the sales functional culture reading down, and by the organization’s meeting culture reading across, at the same time. And every cell, in both directions, is either deliberate or accidental. In most organizations almost every cell is accidental.

The Matrix Repeats at Every Level

The structure is fractal. It nests, and it repeats at every scale. Zoom into any single function and you find the same matrix again inside it: the function contains departments, the departments contain teams, and each one has its own version of the activities across the top. A team has its own meetings-feedback-decisions matrix. So does the department. So does the function. So does the whole company. Same structure, different scope.

This is why the same approach to building culture works whether you lead a team of five or an organization of fifty thousand. The methodology does not change with scale. Only the scope does. A team lead can make their team’s matrix deliberate this week. A CEO can make the enterprise matrix deliberate over a year. It is the same work at a different altitude. And it means you do not have to start at the top. You can start with the one cell you control and build out from there.

Why Subcultures Collide

Because each subculture develops its own accidental way of thinking and working, they collide wherever they have to meet. And they collide hardest across functions, at the seams of the matrix, because that is where the fewest defaults are shared.

Finance operates with caution, precision, and long time horizons. Sales operates with urgency, optimism, and speed. Engineering operates with rigor, sequencing, and a need to understand why before committing. None of these is wrong. They are rational adaptations to different work. But when sales needs something from finance, it is not simply two departments with different goals. It is two subcultures with fundamentally different ways of thinking colliding at a seam where almost nothing is shared. Sales experiences finance as slow and obstructive. Finance experiences sales as reckless and impatient. Both are right, from inside their own subculture, and both are translating badly across the gap.

Within a function, people share enough defaults that the friction is manageable. Across functions, there is often no shared language, no shared rhythm, no shared standard for what good looks like, so the collision is sharpest exactly where the organization most needs the functions to work together. The handoff between functions is where the friction concentrates, because that is the cell where two different subcultures have to meet and neither one was built to.

Think about the last cross-functional fight you were in. Were the two sides actually enemies, or were they two subcultures that had never agreed on how to work together, each convinced the other was the problem?

How Subcultures Become Silos

The same belonging that makes a team feel like home is what eventually walls it off from the rest of the organization. The bond that holds a tribe together internally is the bond that defines everyone outside it as other. That is the emotional seed of the silo, and it is felt long before it shows up on any org chart.

In the matrix, a silo is what happens when the vertical gets strong and the horizontal stays weak. When functional cultures are powerful and the shared how-we-work-together culture is thin, each column hardens into its own world. Sales optimizes for sales. Engineering optimizes for engineering. Nobody is reading the matrix across. The functions stop working together not because anyone intends it, but because there is no strong horizontal culture tying the rows together. The walls go up by default.

This is one of the most common and most expensive cultural pathologies in organizations, and the matrix finally shows where it comes from. What to do about it is a harder question than it looks, because the fixes everyone reaches for, the reorgs, the liaison roles, the collaboration values, all fail for the same reason. That failure, and what actually works, deserves its own page.

There is a particular toxicity that grows in this soil, and I knew its pull as an executive: in a weak horizontal culture, budget, headcount, and territory become a fixed pie, and fighting to expand your function’s share feels exactly like good leadership. It is the silo wearing the mask of doing your job. The next page takes that trap apart fully, why it hides so well, why every common fix for silos fails, and how a shared commitment finally makes the zero-sum game visible for what it is.

The Way Out: Make the Matrix Deliberate

The entire methodology of Culture by Commitment is about moving cells from accidental to deliberate, using shared behavioral commitments, the precise language that installs the right way of thinking and behaving in the moments that matter. And the matrix maps exactly where the four types of commitments live.

True North commitments. These sit above the matrix entirely. They name who the organization is, where it is going, and what it stands for: the identity every cell inherits before any work begins.

Core commitments. These are the global commitments, the small set every person in every function lives by, like Speak the Truth with Respect. They do not belong to a row or a column. They blanket the entire matrix, the same language in every cell, which makes them the deepest connective tissue an organization has.

Operating commitments. These run vertically, and they work at any altitude: a team, a department, or a whole function. They encapsulate how that group does its own work and what it is there to win at, making a column coherent without making it a silo. Because the matrix is fractal, so are they.

Activity commitments. These anchor to a row of the matrix. They make one domain, meetings, feedback, decisions, deliberate wherever it shows up, in every function at once.

And because the matrix is fractal, you do not need permission or a company-wide mandate to begin. You start with the subculture you live in most and feel most: your team. You make your team’s matrix deliberate, the cell you actually control, and you build out from there. The same work scales up through the department, the function, and the whole organization, because it is the same matrix at every level.

But one pathology of the matrix deserves its own treatment, because it is the most expensive one and the one every leader has fought: the collision that hardens into a wall.

Read next: How to Break Down Silos.