Culture is the sum of organizational schemas
~7 min read
Core Primitive
Culture is not a mysterious force.
It is the emergent result of all the shared mental models — identity, strategy, process, values, risk, authority, time — operating simultaneously in the organization. When you change the schemas, you change the culture. When you try to change the culture without changing the schemas, nothing happens.
Why culture resists change
Organizational culture is the most discussed and least understood concept in management. Leaders invoke it to explain success ("Our culture is our competitive advantage") and failure ("The culture resisted the change"). Consultants are hired to measure it, transform it, and align it. Books are written about building it, fixing it, and scaling it. And despite all this attention, most culture change initiatives fail. McKinsey estimates that 70% of organizational transformations do not achieve their stated goals, and culture resistance is the most commonly cited reason (Kotter, 1996).
The reason culture change fails is that most approaches treat culture as a thing that can be directly manipulated — like an organizational lever that leadership can pull. But culture is not a lever. It is an emergent property — a pattern that arises from the interaction of lower-level components but cannot be changed by addressing the pattern directly. You cannot change the weather by painting the sky. You cannot change organizational culture by designing posters, running workshops, or renaming conference rooms. You can only change culture by changing the schemas that produce it.
This is the insight that makes culture tractable. When culture is understood as a mysterious, unmanageable force, leaders feel helpless. When culture is understood as the emergent result of specific, identifiable, modifiable schemas, leaders have a clear intervention path: identify the schemas, evaluate them, and modify the ones that are producing the undesired cultural pattern.
Culture as emergent property
Emergence is a concept from complexity science: a higher-order pattern that arises from the interactions of lower-order components but has properties that the components themselves do not have. Water molecules are not wet. Individual neurons are not conscious. Individual ants are not intelligent. Wetness, consciousness, and swarm intelligence emerge from the interactions of many simple components following simple rules.
Organizational culture works the same way. No single schema constitutes culture. The identity schema ("We are an engineering company"), the strategy schema ("We win through technical excellence"), the process schema ("Decisions require technical review"), the values schema ("We value depth over breadth"), and the risk schema ("We avoid shipping anything we are not confident in") — each is a simple mental model. But their interaction produces a complex emergent pattern that people experience as "the culture": a deep, technically rigorous, cautious, engineering-dominated culture that values craft over speed and certainty over experimentation.
Change any one schema and the culture shifts. Change the risk schema from "avoid uncertainty" to "embrace experimentation" while keeping everything else the same, and the culture shifts — engineers begin experimenting more, the approval process loosens, the product evolves faster. The shift is not a culture initiative. It is a schema change that produces a culture change as a byproduct.
Philip Anderson's work on complexity in organizations formalized this view: organizations are complex adaptive systems where macro-level patterns (culture, capability, competitive position) emerge from micro-level interactions (individual decisions, conversations, routines) guided by shared rules (schemas). Changing the macro pattern requires changing the micro rules — the schemas that guide the interactions from which the pattern emerges (Anderson, 1999).
The schema interaction map
To understand an organization's culture, map the interactions between its key schemas. The interaction patterns — reinforcement and conflict — determine the cultural pattern.
Reinforcing interactions produce strong, coherent cultures. When the identity schema ("We are an innovation company"), the values schema ("We reward experimentation"), the risk schema ("Failure is learning"), and the process schema ("Lightweight approvals for experiments") all reinforce each other, the culture is strongly innovative. The reinforcement creates cultural inertia — the culture is stable and self-perpetuating because each schema strengthens the others.
Conflicting interactions produce weak, confused cultures. When the identity schema says "innovative" but the risk schema says "risk-averse," the values schema says "customer-first" but the process schema says "engineering decides," the culture becomes incoherent. Members receive contradictory signals about what the organization values and how they should behave. The result is not a blend of the conflicting schemas but a chronic state of organizational confusion where behavior depends on which schema happens to dominate in each specific situation.
Karl Weick's concept of "loose coupling" describes organizations where different parts operate with different schemas — loosely connected rather than tightly aligned. Some loose coupling is healthy: it allows different functions to adapt to their specific contexts. But too much loose coupling produces an organization where the engineering culture, the sales culture, and the support culture are so different that they operate as separate organizations sharing a payroll system (Weick, 1976).
Why direct culture change fails
Understanding culture as emergent explains why direct culture interventions fail. There are three common patterns of failure:
Artifact manipulation. Changing the visible manifestations of culture — office design, dress code, meeting formats, communication tools — without changing the underlying schemas. Open offices do not create collaboration if the authority schema still concentrates decision-making in leadership. Slack channels do not create transparency if the information schema still restricts access to "need to know." The artifacts change. The schemas persist. The culture persists.
Value proclamation. Announcing new values without changing the incentive, promotion, and resource allocation schemas that determine actual behavior. "We now value innovation" is a proclamation. Promoting someone who failed at an innovative experiment, funding projects without guaranteed ROI, and creating a process for rapid experimentation — these are schema changes. Without the schema changes, the proclamation is empty. Employees learn quickly that the new values are words without consequences, which reinforces cynicism.
Training programs. Teaching people new behaviors without changing the organizational systems that reward old behaviors. A collaboration training program sends people back to an incentive system that rewards individual performance. A leadership development program sends managers back to an authority schema that punishes independent decision-making. The training produces temporary behavior change that decays within weeks as the unchanged schemas reassert their influence. Timothy Wilson's research on the limits of training interventions found that behavior change requires changes in the environment that supports the behavior, not just in the individual's knowledge or motivation (Wilson, 2011).
Schema-level culture change
Effective culture change works at the schema level. It identifies the specific schemas that produce the undesired cultural pattern and modifies them directly.
Step 1: Map the current schemas. Using the methods from Making organizational schemas explicit, surface the organization's operating schemas across all categories: identity, strategy, process, values, risk, authority, time. Map their interactions — which schemas reinforce each other and which conflict.
Step 2: Identify the target schemas. Determine which schemas are producing the undesired cultural pattern. If the culture is too risk-averse, the target schemas include the risk schema ("failure is punished"), the process schema ("everything requires approval"), and possibly the incentive schema ("reliability is rewarded more than innovation").
Step 3: Design schema modifications. For each target schema, design a concrete change. Not "be less risk-averse" but "create a fast-track approval process for experiments under $10K" or "include 'experiments attempted' in performance reviews alongside 'projects completed.'" The modification must be specific enough to be implemented and observable enough to be verified.
Step 4: Implement and reinforce. Implement the schema changes and reinforce them through leadership behavior, incentive alignment, and consistent messaging. Leadership behavior is the most powerful reinforcement mechanism — when leaders visibly act in accordance with the new schemas, especially when the old schemas would be easier, the new schemas gain credibility.
Step 5: Monitor emergence. Watch for the emergent cultural pattern to shift. Culture change is slow because emergence is slow — the new schemas must propagate through the organization and interact long enough to produce a new stable pattern. Expect months, not weeks.
The Third Brain
Your AI system can help you analyze culture as a system of interacting schemas. Describe your organization's schemas across all categories and ask: "Map the interactions between these schemas. Which reinforce each other? Which conflict? What cultural pattern would emerge from these interactions? What is the smallest number of schema changes that would produce the largest cultural shift?"
The AI can also model the impact of proposed schema changes: "If we change the risk schema from 'failure is punished' to 'failure is data,' what would happen to the interaction with the process schema, the incentive schema, and the authority schema? Would the change propagate or would other schemas resist it?" This modeling reveals which schema changes are self-reinforcing (they change the interaction pattern in ways that support further change) and which are self-defeating (they conflict with unchanged schemas that will override them).
For ongoing culture monitoring, use the AI to periodically assess the organization's schema landscape: "Based on these recent decisions, communications, and organizational events, have our operating schemas shifted? Are the schemas we intentionally changed actually operating differently, or have they reverted? Are any schemas drifting in unexpected directions?" The assessment keeps culture change on track by monitoring the schemas that produce the culture rather than surveying the culture directly.
From coherence to conflict
A coherent culture — one where schemas reinforce each other — is powerful but not always adaptive. The same schema coherence that produces consistent behavior can also produce rigidity: the organization becomes very good at one thing and unable to do anything else. And in organizations of any size, perfect schema coherence is rare. Different departments, functions, and levels develop different schemas — and these schema conflicts produce coordination failures that can be as consequential as the schemas themselves.
The next lesson, Schema conflicts within organizations, examines schema conflicts within organizations — what happens when different parts of the organization hold incompatible mental models, and how to diagnose and resolve the conflicts that result.
Sources:
- Kotter, J. P. (1996). Leading Change. Harvard Business School Press.
- Anderson, P. (1999). "Complexity Theory and Organization Science." Organization Science, 10(3), 216-232.
- Weick, K. E. (1976). "Educational Organizations as Loosely Coupled Systems." Administrative Science Quarterly, 21(1), 1-19.
- Wilson, T. D. (2011). Redirect: The Surprising New Science of Psychological Change. Little, Brown.
Put it into practice
Exercise
Map your organization's culture as a set of interacting schemas. List the organization's operating schemas in five categories: (1) Identity — 'We are a [type] organization.' (2) Strategy — 'We win by [approach].' (3) Process — 'Work flows through [mechanism].' (4) Values — 'We prioritize [X] over [Y].' (5) Risk — 'We treat uncertainty by [approach].' For each schema, write one sentence describing the actual operating assumption (not the aspirational version). Then examine the interactions: Do the schemas reinforce each other (the strategy schema and the values schema point in the same direction) or conflict (the strategy schema says 'move fast' but the risk schema says 'avoid mistakes')? The pattern of reinforcement and conflict is the organization's culture — understood not as a vague feeling but as a specific, analyzable system of interacting mental models.
More on putting it into practice
See it in action
A logistics company decided to transform its culture from 'command-and-control' to 'empowered and innovative.' Leadership hired a culture consultancy, ran workshops, redesigned the office space with open layouts and collaboration zones, introduced an 'innovation hour' every Friday, and created a 'culture committee' of employee volunteers. Eighteen months later, the culture survey showed no meaningful change. Employees still described the culture as hierarchical and risk-averse. The culture initiative had changed artifacts — the visible manifestations of culture — without changing the underlying schemas. The authority schema remained intact: decisions still required approval from two levels up. The risk schema remained intact: any initiative that failed was treated as a career setback. The time schema remained intact: quarterly targets dominated every planning conversation. The values schema remained intact: compliance and reliability were rewarded; experimentation and learning from failure were not. The open office layout meant people sat closer together while still deferring to the same hierarchy. The innovation hour meant people had permission to brainstorm ideas that would never survive the approval process. The culture committee had no authority to change the schemas that produced the culture. The CEO eventually realized the problem: 'We changed the wallpaper and expected the house to be different.' Real culture change required changing the operating schemas — modifying the approval process, revising the incentive structure, shifting the risk schema from 'failure is a setback' to 'failure is data.' These changes were harder, slower, and more threatening to existing power structures than workshops and open offices. But they were the only changes that could actually produce a different culture.
Watch for the failure mode
Trying to change culture directly rather than changing the schemas that produce it. Culture is an emergent property — it arises from the interaction of lower-level components (schemas) and cannot be changed by addressing the emergent property itself. Telling people to 'be more innovative' does not change the risk schema that punishes failed experiments. Telling people to 'collaborate more' does not change the incentive schema that rewards individual performance. Culture change programs that target culture directly — through workshops, slogans, and artifacts — produce the appearance of change without the substance, because the underlying schemas that produce the culture remain untouched.
Make it stick
This lesson synthesizes the previous six lessons in Organizational Schemas by showing how identity schemas (Organizations run on shared schemas), implicit schemas (Organizational schemas are often implicit), explicit schemas (Making organizational schemas explicit), strategy schemas (Strategy is an organizational schema), process schemas (Process is an organizational schema), and values schemas (Values are organizational schemas) combine to produce organizational culture. Culture is not a seventh type of schema — it is what you get when all the schemas operate together. Return to Organizations run on shared schemas and trace the journey through each schema type, recognizing how each contributes to the emergent whole. Look forward to Schema conflicts within organizations, which examines what happens when organizational schemas conflict — when different parts of the organization hold incompatible mental models that produce coordination failures.
Practice
Map Organizational Culture as Interacting Schemas in Miro
Create a visual map of your organization's culture by documenting five categories of operating schemas and analyzing how they reinforce or conflict with each other. This practice transforms abstract culture into a concrete system of interacting mental models.
- 1Open Miro and create a new board titled 'Organizational Schema Map.' Create five vertical columns labeled: Identity, Strategy, Process, Values, and Risk. Use Miro's text tool to add these column headers across the top of your board.
- 2In each column, create 2-3 sticky notes using Miro's sticky note feature describing the actual operating assumptions (not aspirational statements) for that schema category. For Identity write 'We are a [type] organization,' for Strategy write 'We win by [approach],' for Process write 'Work flows through [mechanism],' for Values write 'We prioritize [X] over [Y],' and for Risk write 'We treat uncertainty by [approach].'
- 3Use Miro's connector arrows to draw relationships between schemas that reinforce each other. Select the arrow tool and connect schemas that point in the same direction or support each other, labeling each arrow with a brief note like 'reinforces' or 'enables.' Use green arrows for reinforcing relationships.
- 4Use Miro's connector arrows in red to identify conflicts between schemas. Draw red arrows between schemas that contradict or undermine each other, labeling each conflict with a specific note like 'Strategy says move fast but Risk says avoid mistakes' or 'Values prioritize quality but Process optimizes for speed.'
- 5Add a text box at the bottom of your Miro board summarizing the culture pattern you've uncovered. Write 2-3 sentences describing whether your organization's culture is characterized by reinforcing schemas (aligned culture), conflicting schemas (fragmented culture), or a specific mix, noting which conflicts are most significant for organizational performance.