Table of Content
- Your Founder’s Voice Stops Being the Loudest One in the Room
- Communication Has to Become a System, Not a Vibe
- Rituals Don’t Survive Growth on Their Own — Somebody Has to Rebuild Them
- Leadership Conflict Gets Louder, Not Quieter, Under Growth Pressure
- Decide What You’re Actually Trying to Protect
- Real-World Examples of Leadership During Scale
- A Simple Leadership Framework for Scaling
- The Human Side of Growth
- Final Leadership Thoughts
There’s a moment every founder remembers, even if they can’t pin the exact date.
It’s the day you walk into your own office and don’t recognize half the faces in the kitchen.
Not because anything went wrong. Because it worked. You hired. You grew. And somewhere between employee 30 and employee 80, the company you built stopped being a company you could hold in your head.
Patty McCord, who ran talent at Netflix from 1998 to 2012 and later coined the “stand on a chair” problem, has a name for the exact instant this happens: it’s when a leader gets up on a chair to talk to the whole staff and someone in the back yells, “We can’t hear you.” That’s the signal. The company has outgrown the room, literally and organizationally.
This piece isn’t about the early days — the free desks, the donut Wednesdays, the founders who still know everyone’s dog’s name. It’s about the part nobody puts on a recruiting page: the messy middle, where the culture that got you to 8 people starts to buckle under the weight of 80.
At 20 people, the founder’s behavior basically is the culture. Say something’s important enough times, model it enough times, and the whole team absorbs it by osmosis. No handbook required.
Somewhere around 80, that stops working. The founder is in board meetings, investor calls, and strategy sessions — not sitting three desks away from the newest hire. The loudest voice in most people’s daily experience is now their manager, not the founder. And those managers were usually hired for what they could ship, not for their ability to carry culture forward.
This is where subcultures start creeping in. Engineering develops one set of norms. Sales develops another. Nobody planned it. It just happens when the signal that used to come from the founder gets quiet.
Takeaway:
The job isn’t to stay the loudest voice — you can’t, past a certain size. The job is to make sure the people who are now the loudest voices (your first managers) were trained in the things that made the early team work: direct communication, fast feedback, admitting “I don’t know yet” without losing the room.
John Foley, Peloton’s co-founder, put it plainly once the company crossed a few hundred people: it was great at 50, when he was a big enough presence that the founding team alone could carry the culture. Past that, “that doesn’t scale.”
Facebook’s former chief product officer Chris Cox has said almost every founder he’s talked to notices something strange happening once headcount clears roughly 150 — communication that used to be effortless suddenly requires actual structure.
You see this pattern everywhere once you’re looking for it. At Quartz, the founders responded by building a 10-person operating committee that met weekly just to keep information flowing across a company that had outgrown hallway updates. They started writing down company history for new hires — something that used to just get told over lunch.
That’s the real shift. Information used to move by osmosis. Now it needs a mechanism, or it stops moving at all.
Takeaway:
The first sign you’ve outgrown informal communication isn’t chaos — it’s quiet. People stop asking questions not because they know the answers, but because they’ve stopped expecting to get one. Build the mechanism (weekly syncs, a written company history, regular all-hands) before the silence sets in, not after.
Every early-stage team has its version of donut Wednesday. The thing that isn’t in the job description but somehow does more for retention than the salary does.
The hard truth: those rituals were never really about the donuts. They worked because everyone was close enough, physically and organizationally, for them to mean something. Add 60 more people spread across departments and floors, and the same ritual can start to feel like something only “the originals” are really part of.
The fix isn’t nostalgia. It’s rebuilding the feeling on purpose, at the new scale. That might mean monthly demo days where any team can show what they’re working on. Quarterly sessions where leadership goes first in admitting what didn’t work. Onboarding buddies paired across departments instead of within them, so new hires build relationships outside their own function from day one.
Takeaway:
You can’t keep the exact ritual. You can keep the reason it mattered — shared identity, shared struggle — and build a new version sized for who you are now.
Small teams paper over disagreement pretty easily. There’s no time for it, and everyone’s too busy building the thing.
Growth removes that cover. More money on the table, more people watching, more decisions that actually matter — and the cracks between co-founders or senior leaders that used to stay behind a closed office door start to show up in how the whole company feels. Research often cited on this points to leadership and co-founder dysfunction as one of the most common reasons high-potential startups stall out, not lack of market or product.
This is uncomfortable to write about because it’s rarely dramatic in the moment. It’s a strategy disagreement that used to resolve in five minutes over lunch, and now takes three meetings and still doesn’t resolve. It’s two leaders who used to finish each other’s sentences and now schedule separate 1:1s with the same VP to get their version in first.
Takeaway:
Don’t wait for a blow-up to address a widening gap between leaders. The moment disagreements start requiring more structure to resolve than they used to, that’s the moment to bring in outside facilitation — a coach, an advisor, a board member who isn’t inside the fight — not after it’s already a story employees are telling each other.
Here’s the thing nobody tells you before you scale: you can’t protect the feeling of being small. That version of the company is genuinely gone once you’re 80 people, and grieving it a little is normal.
What you can protect is what the feeling was actually standing in for — that people were seen, that effort was noticed, that leadership was honest about what was and wasn’t working. Those things don’t require a small headcount. They require intention, once instinct stops being enough.
The founders who navigate this well aren’t the ones who resist structure the longest. They’re the ones who figure out, early, which three or four behaviors actually made the early culture worth having — and then build systems, deliberately, to keep those specific things alive while everything else about the company changes around them.
As Airbnb expanded globally, its leadership invested heavily in preserving culture through structured onboarding, leadership principles, and consistent internal communication. Rather than relying on informal traditions, the company documented its values so they could scale alongside the business.
Leadership lesson: Culture must be intentionally designed before rapid hiring begins.
Shopify encouraged leaders to write instead of relying solely on meetings. Clear documentation helped distributed teams stay aligned while reducing confusion and repeated conversations.
Leadership lesson: Empowerment scales better than centralized control.
Atlassian built a culture centered on autonomy and transparency. Teams were trusted to make decisions close to the work while leaders focused on strategy, alignment, and long-term priorities.
Although every startup is different, these companies share one principle: they treated leadership as a system that could grow—not just as the responsibility of a few individuals.
Leadership lesson: Documentation becomes a competitive advantage as organizations grow.
As your company grows, focus on five priorities.
| Stage | Leadership Focus |
| 8 People | Build the product and win customers |
| 20 People | Define culture and hire deliberately |
| 40 People | Create management layers and repeatable processes |
| 60 People | Strengthen communication and accountability |
| 80+ People | Build leaders who can scale the next stage of growth |
Leadership isn’t about doing more work yourself.
It’s about enabling more people to do great work together.
Growth is exciting, but it can also be uncomfortable.
People who joined during the earliest days may struggle with change. New managers bring fresh ideas that challenge established habits. Founders may feel disconnected from the close-knit team they once knew personally.
These moments are normal.
The best leaders acknowledge the emotional side of scaling instead of pretending it doesn’t exist. They explain why changes are happening, listen to concerns, and stay visible even as the organization becomes larger.
When people understand the purpose behind change, they’re far more likely to support it.
Scaling from eight people to eighty isn’t simply a hiring milestone. It’s a leadership transformation.
Every new employee adds capability, but also complexity. Communication becomes harder. Decisions require more structure. Culture needs intention. Managers need coaching. Systems become essential.
The leaders who succeed aren’t those who try to stay involved in everything. They’re the ones who create an environment where talented people can make good decisions, solve problems, and move the business forward without constant supervision.
In the end, the measure of great leadership isn’t how much control you keep. It’s how much capability you build in others. When your team can thrive without relying on you for every answer, you’ve done more than scale a company—you’ve built an organization that can keep growing long after the startup phase is over.