I’ve watched this pattern unfold enough times to recognize it before it becomes a crisis. A founder builds something small with a particular ethos – maybe it’s radical transparency, or a specific way of making decisions, or an unspoken understanding about what work means in that space. For the first few years, this works because everyone in the room either came from the founder or was hand-selected by them. The culture is less something documented and more something lived. Then the company grows. New people arrive who never met the founder. Departments form. Processes become necessary. And somewhere around 40 or 80 or 150 people, someone realizes the culture that felt so natural at ten people no longer fits.
The tension isn’t usually about the founder being wrong. It’s about scale introducing friction that wasn’t present before. A founder who made every hiring decision personally can’t do that anymore. A communication style that worked in a room of eight becomes noise in a room of eighty. An informal decision-making process that felt empowering at small scale starts to feel chaotic and exclusionary once you have multiple teams working in parallel. The culture doesn’t break because it was bad. It breaks because the conditions that allowed it to function have fundamentally changed.
The Hidden Cost of Unwritten Rules
Most founding cultures rely heavily on implicit knowledge. People learn how things actually work by observation and osmosis, not by reading a handbook. This works remarkably well when the group is small and homogeneous. But it creates a specific problem as the company grows: new people spend months or years trying to decode unwritten rules that the founder never had to articulate because they were self-evident to the original group.
I’ve seen this play out in hiring decisions, project prioritization, and conflict resolution. A new manager arrives and assumes the stated values are the actual values. They discover through friction that the real operating system is something different – something that only makes sense if you’ve been in the room with the founder long enough. This isn’t dishonesty. It’s just that the founder’s implicit worldview was so consistent that it never needed to be made explicit. Once you have people from different backgrounds and experiences, that assumption breaks.
The founders I’ve worked with who navigated this well didn’t try to preserve the unwritten culture. They did something harder: they made it explicit. They articulated what they actually valued, which often meant discovering that some of what they thought was core culture was actually just “how we happened to do things when we were small.” That distinction matters. Some things were genuinely important to the mission. Others were just artifacts of early-stage constraints.
When Founder Values Become Scaling Friction
There’s a particular kind of founder who builds culture around their personal way of working. Maybe they’re an early riser and the culture becomes one of early risers. Maybe they’re detail-oriented and the culture becomes one where every decision is debated extensively. Maybe they’re risk-tolerant and the culture celebrates bold moves without much process. These aren’t bad things. They often create real competitive advantages at small scale.
But they also create a specific problem: the founder’s personal operating system becomes embedded in the organizational operating system. When you’re small, that’s fine. When you’re large, it becomes a constraint. You can’t hire people who work differently because the culture has no space for different working styles. You can’t move fast in some domains because the founder’s need for control or consensus slows everything down. You can’t build resilient systems because everything still depends on the founder’s presence and decision-making.
I watched one founder whose strength was in relationship-building and intuitive decision-making build a company that worked beautifully at 30 people. At 100 people, that same strength became a bottleneck. Every significant decision still ran through him. He could sense the right call in a room of thirty people. In a company of a hundred, that intuition became less reliable, but the culture had been built around trusting his instincts. The company didn’t fail, but it hit a wall where it couldn’t move faster than his personal bandwidth allowed.
The Founder-Culture Mismatch
Sometimes the mismatch is even more direct: the founder’s personal values start to diverge from what the organization actually needs. A founder who thrives on chaos and improvisation might have built something that needs stability and process to scale. A founder who is deeply technical might have built a company that now needs someone who is primarily a manager. A founder who values loyalty above all else might have built a company that needs people willing to challenge the status quo.
These aren’t failures of character. They’re just misalignments between what made someone effective at founding and what the organization needs to survive at the next stage. I’ve seen founders who recognized this and brought in operators who could build the systems and structures the company needed. I’ve also seen founders who fought it, trying to preserve their way of working even as it became increasingly incompatible with the organization’s needs.
The companies that handled this best didn’t pretend the founder’s values weren’t important. They honored what the founder built while also being honest about what the organization needed to become. Sometimes that meant the founder stepping back from day-to-day operations. Sometimes it meant bringing in a COO or head of operations who could build the infrastructure the founder never wanted to build. Sometimes it meant the founder evolving their own approach, which is harder than it sounds because it requires admitting that your way of working, which got you here, won’t get you there.
The Real Work of Culture Evolution
What I’ve noticed is that the companies that navigate this transition successfully don’t treat it as a problem to solve. They treat it as a natural phase of growth that requires active management. This means being willing to examine what the culture actually is, not what the founder wishes it was. It means asking which values are truly non-negotiable and which are just habits. It means sometimes making the hard choice to let go of something that worked at small scale because it’s preventing growth.
The founder’s role doesn’t disappear in this transition. It changes. Instead of being the embodiment of the culture, the founder becomes someone who helps the organization articulate and preserve what actually matters while letting go of what doesn’t. This is harder than it sounds because it requires a kind of humility that not all founders have. It means accepting that other people might do things differently than you would, and that different doesn’t mean wrong.
I’ve seen organizations where this transition happened smoothly and organizations where it became a crisis. The difference wasn’t usually about how good the original culture was. It was about whether the founder and the leadership team were willing to acknowledge that something needed to change, and whether they could do that without losing what made the organization special in the first place. The companies that struggled were the ones that pretended nothing needed to change, or that changed everything and lost the thread of what made them distinctive.
