I’ve watched this transition happen dozens of times, and it’s rarely graceful. A founder who built a company from nothing suddenly finds themselves struggling. They’re not failing because they’ve lost competence – they’re failing because the job has become something entirely different, and nobody told them.
The shift isn’t gradual. There’s a threshold somewhere between 50 and 150 people where the old approach stops working. Before that point, a leader can know most of their team by name, understand what everyone is working on, and make decisions quickly because information flows directly to them. After that point, they can’t. The structure that made them effective becomes the thing that breaks the organization.
What tends to happen is that leaders keep doing what made them successful, just harder. They try to be everywhere, stay involved in every decision, maintain those direct relationships. They work longer hours. They become bottlenecks without realizing it. Projects stall because people are waiting for their input. New hires feel like they’re working for an absent leader because the leader is stretched too thin to actually lead them. The frustration builds on both sides.
When Personal Relationships Stop Scaling
Early on, leadership is almost entirely relational. You know your team. You understand their strengths, their struggles, what motivates them. You can have a conversation with someone and understand the context of their work immediately because you’ve been in the room when decisions were made. Trust is built through proximity and consistency.
Around 40 or 50 people, this starts to strain. A leader can still theoretically know everyone, but the time investment required becomes unsustainable. More importantly, the information load changes. When you have 8 people reporting to you, you can hold the state of their work in your head. When you have 15, you can’t – not reliably. When you have 30, you’re not even trying anymore, though you might not admit it.
What I’ve observed is that leaders often compensate by becoming more controlling, not less. They sense they’re losing grip on what’s happening, so they ask for more updates, more meetings, more visibility. This creates a different problem: the organization becomes slower because everything flows through them. People stop making decisions and start waiting for approval.
The real shift requires accepting that you can’t know everything anymore. You have to build systems and trust structures that work without your direct involvement. This is harder than it sounds because it feels like losing control, even though it’s actually the only way to maintain any control at scale.
The Emergence of Middle Management
This is where many growing organizations stumble. The founder doesn’t want middle management – it feels bureaucratic, slow, like it’s adding layers that weren’t there before. And they’re right that it changes things. But the alternative is worse.
Without middle management, you have a flat structure that only works up to a certain size. Once you exceed that, you need people whose primary job is to translate strategy into execution, to manage the work of others, and to filter information up and down the organization. These people aren’t overhead. They’re the only way the organization functions at scale.
The problem is that founders often promote their best individual contributors into these roles and then expect them to work the same way they did before. A brilliant engineer becomes an engineering manager and suddenly they’re in meetings all day instead of writing code. They’re frustrated. The organization is frustrated because they’re not coding anymore. Nobody’s happy.
What works better is recognizing that management is a different skill set entirely. It’s not a promotion for your best people – it’s a different career track. Some of your best individual contributors should stay individual contributors. Others have the temperament and interest for management, but they need to learn it, and they need time to transition into it. This almost always means bringing in experienced managers from outside, at least at first.
Decision-Making Becomes Distributed
Early stage, decisions happen fast because there’s one person making them or a small group of people in constant communication. The founder has a vision, they decide what to do, and it happens.
As the organization grows, this model breaks down. You can’t have the founder making every decision – there aren’t enough hours in the day, and you’re preventing other people from developing judgment and ownership. But if you just let everyone decide everything, you get chaos and inconsistency.
The transition requires establishing clear decision-making frameworks. What decisions can teams make on their own? What decisions require input from leadership? What decisions are strategic and require the founder’s involvement? These boundaries need to be explicit, and they need to be communicated clearly. Most organizations don’t do this well. Instead, there’s ambiguity about who decides what, and people either wait for permission or make decisions they shouldn’t.
I’ve also noticed that as organizations grow, the quality of decisions often goes down in the short term. This is because decisions are slower and involve more people. The founder’s instinct, which was often right, gets diluted by committee thinking. This is a real cost, and it’s worth acknowledging. The trade-off is that the organization becomes less dependent on one person’s judgment, and over time, the quality stabilizes as people develop better judgment themselves.
The Leader’s Role Becomes Increasingly Abstract
One of the hardest things for founders to adjust to is that their job becomes less concrete. Early on, they’re solving problems, building product, talking to customers. There’s immediate feedback. You build something, people use it, you know if it worked.
As the organization grows, the leader’s job becomes about setting direction, building culture, developing other leaders, and making sure the organization is structured to execute. These are real things, but they’re harder to point to. You can’t see the impact of a good culture decision the way you can see the impact of a good product decision. The feedback loop is longer and less direct.
This is where some leaders get restless. They want to get back to building, to doing something tangible. Some of them do – they step back from the CEO role and move into a product or technical role. This is fine if the organization has a strong second-in-command who can take over. But often, the founder tries to do both, and that’s when things fall apart.
The leaders who navigate this well are the ones who find meaning in building the organization itself rather than in the direct work. They care about developing their team, about creating systems that work, about making sure the right decisions get made even when they’re not in the room. This is a different kind of satisfaction, but it’s real.
What I’ve seen repeatedly is that the leaders who struggle most are the ones who don’t acknowledge this shift. They keep trying to be the person who builds and decides and knows everything. They burn out, or they hold the organization back, or both. The ones who succeed are the ones who consciously choose to become a different kind of leader.
