Organizational culture is not your values poster. It is the set of shared assumptions, beliefs, and behaviors that shape how work actually gets done when nobody is watching.
That distinction matters because most founders try to fix culture by updating the poster. The poster is the visible layer. Culture runs underneath it, and it runs whether you designed it or not.
If your team consistently over-promises to clients, that is culture. If they quietly work around broken processes instead of fixing them, that is culture. If they tell you things are fine when they are not, that is culture too. None of those behaviors show up in your stated values. All of them show up in your results.
This post is about reading the culture you have, understanding what drives it at the root level, and then doing something about it.
Schein organizational culture: the model worth knowing
The most useful framework for reading organizational culture comes from Edgar Schein, an MIT organizational psychologist who spent decades studying how culture forms and how it can be changed.
Schein organizational culture theory starts with a simple observation: culture operates at multiple levels simultaneously, and the most powerful level is the one you cannot see.
When Schein talks about culture, he is not talking about ping-pong tables or Friday happy hours. He is talking about the invisible logic that governs how people inside an organization interpret situations and decide what to do. His model gives you a way to look at that logic systematically, which means you can actually work with it instead of just hoping it improves.
The reason Schein's framework has lasted 40-plus years is that it does not describe what culture should look like. It describes what culture actually is. And what it actually is turns out to be layered in ways that explain why surface-level culture initiatives rarely stick.
Levels of culture: what you can see versus what you cannot
The reason culture is hard to change is that it exists at three distinct levels of culture, and most change efforts only touch the top one.
Artifacts are the visible, surface-level outputs of a culture. The way meetings are run. The language people use in Slack. Whether the office is quiet or loud. Whether the leadership team responds to questions publicly or privately. Whether Bogdan, our COO, holds a formal all-hands or drops updates in a shared channel.
Artifacts are easy to observe. They are hard to interpret without knowing what is underneath them. You can walk into a company, see that the team has standing desks and a collaborative open floor plan, and conclude the culture is flat and open. You could be completely wrong. The artifacts tell you what the culture produces. They do not tell you why.
Espoused values are what the organization says it believes. These appear in the employee handbook, in the mission statement, in the quarterly all-hands. "We value transparency." "We put clients first." "We move fast and own our mistakes."
Espoused values are often genuine. The problem is that the gap between what a company says it values and how it actually behaves is where culture lives. A company that espouses transparency but penalizes people who surface problems has told you exactly where the culture stands. The espoused value is a signal. The behavior is the data.
Basic underlying assumptions are the third level, and they are the hardest to see because they are invisible even to the people who hold them. They are the taken-for-granted beliefs about how the world works, how people should relate to each other, and what success means. They do not get discussed because nobody thinks to question them. They just are.
Examples: "The founder's opinion wins any disagreement." "Showing vulnerability is weakness." "Hitting numbers is more important than how you hit them." "Clients will leave if you push back." These are not written anywhere. They are absorbed. They get passed from senior employees to junior ones through the way conversations are shut down, the way escalations are handled, the way wins and losses are narrated.
Schein's point is that lasting culture change requires working at the level of basic underlying assumptions, not just at the level of artifacts or espoused values. If you skip to the bottom level, everything else shifts with it. If you stop at the top, nothing real changes.
Three levels of organizational culture in practice
Understanding the three levels of organizational culture is useful as theory. Applying it in a real company requires translating each level into something observable and actionable.
At the artifact level, do an audit of how your team actually behaves, not how you think they behave. Sit in on a meeting you do not normally attend. Read a thread of internal Slack messages without participating. Look at what information gets escalated and what gets buried. What you observe is a direct read on the artifacts level.
At the espoused values level, write down what your company says it values, then list the last five decisions you made that touched each value. If the decisions match, the espoused value is real. If they do not, the espoused value is aspirational at best and misleading at worst. Both are useful to know.
At the basic underlying assumptions level, you are looking for the invisible rules. The easiest way to surface them is to pay attention to what happens when someone breaks one. An employee raises a concern and gets punished quietly. A process gets bypassed and nobody mentions it. A number gets missed and the team hedges its language. Whatever the reaction reveals, that is an assumption.
Once you can name the assumptions running underneath your culture, you can decide which ones to keep and which ones to displace. Displacement is not quick. Schein spent most of his career studying how long it actually takes. But it starts with naming. You cannot change an assumption you have not made explicit.
Culture and operating systems
Here is where the practical part gets specific.
Organizational culture does not exist independently of the operating system a company runs. The operating system is the set of tools, rituals, cadences, and structures that govern how decisions get made and how performance gets managed. Culture and the operating system interact constantly. The operating system encodes assumptions. The assumptions shape how the operating system is used.
This is why EOS (the Entrepreneurial Operating System developed by Gino Wickman) works for a lot of companies. When you implement the Accountability Chart, the Rocks, the L10 meeting cadence, and the scorecard, you are not just adding tools. You are installing a set of assumptions about how work should flow, who owns what, and how problems should surface. The operating system does the encoding work.
At Sneeze It, we run a hybrid operating system that includes human seats and agent seats on the same scorecard. Radar, our chief-of-staff agent, runs the morning briefing cadence. Tally pushes KPI values from local sources to the team scorecard. Dash owns all ad performance data. Arin, our call center manager, coaches the human calling team through data-driven Slack messages.
Each of those agents encodes assumptions. Radar encodes the assumption that information should surface before humans need to ask for it. Tally encodes the assumption that numbers should be updated continuously, not on a schedule someone remembers. When those assumptions are built into the operating system, they become part of the culture without requiring anyone to repeat them.
That is the most efficient culture-building move available to an operator right now: encode your intended assumptions into the systems that run automatically, rather than relying on repetition, posters, or quarterly all-hands messages.
You can read more about how this plays out when AI agents and humans share the same scorecard and how the agent seat on an org chart gets defined before it gets filled.
Frequently asked questions
What is organizational culture in simple terms? Organizational culture is the shared set of assumptions and behaviors that determine how people in a company make decisions when the rules do not tell them what to do. It is not what you say you value. It is what you actually do, and why you do it that way without thinking about it.
What are Schein's three levels of organizational culture? Edgar Schein's model identifies artifacts (visible behaviors and outputs), espoused values (what the organization says it believes), and basic underlying assumptions (the invisible, taken-for-granted beliefs that actually drive behavior). Schein's argument is that lasting culture change requires working at the assumption level, not just the artifact level.
Can organizational culture be changed on purpose? Yes, but it takes longer than most leaders expect and requires working at the level of basic underlying assumptions, not just stated values. The fastest path is changing the operating system and rituals that encode assumptions, because behavior repeated consistently in a structured cadence eventually becomes belief.
How do you read an organization's culture accurately? Observe behavior rather than asking about values. Watch what happens when someone breaks an unwritten rule. Look at what information gets buried versus escalated. Pay attention to the gap between what leadership says and what leadership does. The gap is the culture.
How is culture different from values? Values are what an organization says it believes. Culture is what it actually does. Espoused values and lived culture sometimes match. When they diverge, the culture always wins. Aligning them requires making the implicit explicit, which is uncomfortable but necessary.
Run it in OTP
The assumptions running your culture are invisible until you name them. OTP gives your team a shared operating surface where roles, accountabilities, and KPIs make those assumptions visible and queryable in real time.
In Claude Desktop or Cursor or any MCP client, add this block:
"otp": {
"command": "npx",
"args": ["-y", "@orgtp/mcp-server"]
}
Restart the client. Then ask: "Use OTP to show me which seats on my org chart have defined KPIs and which do not."