Back to all topics
An Essay · Vol. 02 · Culture as an OS

Building Cultures
That Help Scale.

The kernel, your non-negotiable values, stays fixed. The shell, how ownership and decisions actually work, needs to be rewritten at every growth stage.

Topics I Think About02 of 05

A pattern I have lived through more than once, and watched many of my peers live through, is the moment when a growing organization quietly stops feeling like the one you started with.

The all-hands lands differently. Decisions take a little longer. New hires describe the company in ways that don't quite match what the early team would say. Nobody has done anything wrong. The culture is just no longer doing what it used to do on its own.

I've sat through this transition at many different scales. From small early-stage teams, through the messy middle stages where things grow faster than the operating model, all the way up to large global organizations. Each stage has its own version of this moment. The shape changes, the symptoms change, but the underlying question is the same. The way the team works has outgrown the way it was originally set up to work.

In that moment, the natural instinct, certainly mine and many of my peers', is to reach for the familiar tools. Write down the values again. Run a culture workshop. Hire a Head of Culture. None of that is misplaced; it is often necessary. But in my experience, it has rarely been sufficient on its own. The deeper issue, when I look back at the transitions I've lived through, was usually that the culture was built for a different scale, and the operating layer underneath it hadn't been redesigned to match where the organization was now.

The way I've come to think about it is this. Culture at scale behaves like an operating system. The kernel, your non-negotiable values, stays fixed. The shell, how ownership, decisions, and processes actually work, needs to be rewritten at every growth stage. Organizations seem to struggle when they freeze the shell instead of evolving it.

A note on the evidence

This is not only a metaphor. There is well-known research from anthropologist Robin Dunbar showing that humans can maintain only a limited number of stable relationships before group cohesion starts to strain, which is why some companies, like W.L. Gore, deliberately cap facility sizes and build new ones rather than letting existing ones grow further. Patty McCord, Netflix's former chief talent officer, has written that the conversations she has with CEOs about cultural transitions repeat themselves at almost every growth stage. The fracture isn't a failure of values. It is a structural transition that asks the leader to redesign the operating layer.

Three principles

How I think about redesigning the operating layer.

01
Principle No. 01

Keep the kernel small, fixed, and sacred.

The non-negotiables, how you treat people, how you handle truth, what you'll refuse to do for a deal, should be few, and rarely up for revision. A pattern I've noticed in many companies, including ones I've been part of, is that the value list grows too long with the best of intentions, and then quietly dilutes further when growth pressure hits. A short, stubborn kernel is what lets everything else change without the company losing itself.

02
Principle No. 02

Redesign the shell at each stage, deliberately.

Ownership in a small team often looks like "everyone owns everything." That same instinct, at scale, can become paralysis. From what I've seen, each growth stage seems to call for a different version of how decisions get made, how performance is measured, how outcomes are owned. The leaders I admire, the ones who scale well, tend not to wait for the shell to break. They redesign it on the way up. And they're willing to retire processes that worked beautifully a year ago and have quietly started getting in the way.

One thing I've personally cared about, even at the largest team sizes I've led, is staying approachable and directly connected to the people doing the work. That has only been possible because I kept redesigning the shell underneath me, the cadence of communication, the structure of decision rights, the way information flowed, so that scale didn't quietly turn into distance.

03
Principle No. 03

Keep processes in service of outcomes, never the other way around.

This is the principle that, in my experience, quietly determines whether a culture stays alive or hardens into bureaucracy. Processes are useful as long as they serve the outcome. The moment a team starts optimizing for the process, running the meeting because the meeting is on the calendar, filling the template because the template exists, culture has begun to invert. The healthier organizations I've worked with question their own processes regularly. The aging ones tend to defend them.

Underneath all of this is something I learned the hard way. Clarity from leadership, visibility in decision-making, and helping people see the bigger picture isn't a project. It is a continuous job. I've done it reactively, after an incident made it obvious. I've done it by stepping into someone else's shoes when I should have done so earlier. And I've done it because I was lost once myself, and that probably taught me more empathy than any framework could.

The cultures I've seen scale well aren't the ones with the best values posters. They are the ones where leaders keep the kernel sacred, keep redesigning the shell, and keep processes accountable to outcomes, rather than the reverse.

A question to sit with
If you redesigned the operating layer of your team this quarter, what would you stop doing first?
Samir Deolikar · Topics I Think About