Scaling Culture: Why Growth Breaks Old Habits

At eight people, you barely need an org chart. Everyone knows who handles the angry client, who can fix the billing issue, who has the weird historical knowledge about that one account, and who needs to be pulled into a decision before somebody does something expensive. That informality can work beautifully, right up until scaling culture requires more than shared memory and proximity.

Someone has a question? They ask across the room. Something changes? Everybody hears about it. A customer has an unusual request? You probably know enough about the situation to make the call yourself.

It feels fast. Flexible. Maybe a little chaotic, but it works.

… and then you grow.

Now there are 27 people. Then 34. Then 49.

And suddenly the company that used to move quickly has meetings about why things aren’t moving quickly.

Welcome to growing pains. (Except I don’t think “growing pains” explains enough.)

Your culture didn’t suddenly break because you hired employee number 39. Your people didn’t collectively lose their common sense. And new employees aren’t necessarily less committed than the people who were there at the beginning.

The system that worked when everyone shared context stopped working when they didn’t.

That’s a scaling culture problem. And if you treat it like a morale problem, a hiring problem, or a “people just need to communicate better” problem, you’re probably going to spend a lot of time fixing the wrong thing. (Read: $$$)

Key Topics

Why small-team culture works without much structure
What changes as your company grows
The hidden role of shared context
Why “we need better communication” usually isn’t specific enough
How founders accidentally become the cultural infrastructure
What needs to become explicit as you scale
How to tell whether you’re experiencing scaling strain

At 8 People, Proximity Does a Lot of Work for You

Small teams have an advantage we don’t talk about enough: Everybody knows everything – or close enough.

You know what sales promised because you heard the call. Your operations person knows why a deadline moved because she was sitting three feet away when the customer changed it. The person handling invoicing knows that this client gets unusual payment terms because you’ve been working with them since 2009.

Nobody wrote half of this down.

Nobody formally assigned decision rights.

You may not even have managers yet. And somehow, things still happen.

That can create a dangerous conclusion: This is our culture.

Some of it is. The trust might be real. The willingness to jump in and help might be real. The speed might be real. The lack of ego might be real.

But some of what you’re calling culture is actually proximity, while some is shared history, some is direct access to you, some is a tiny communication network where information can travel without much effort, and some is eight smart people quietly filling gaps that nobody has formally acknowledged yet.

That can work surprisingly well… until it doesn’t.

Growth Doesn’t Just Add People. It Adds Distance.

Going from eight employees to 40 isn’t the same company with 32 additional humans dropped into it.

Everything changes – the relationships, the information flow, the number of handoffs. People specialize into specific roles. Managers appear. Departments form. Customers start interacting with employees you’ve never directly trained.

And somewhere in all that growth, the shared context starts thinning out.

At eight people, most everyone has heard some version of the same story. They were there for the messy client situation, the decision that didn’t work, or the conversation that changed how you do things. By 40, that’s no longer possible. So people start making decisions based on different pieces of the same story.

The new employee in operations wasn’t there when you learned why you stopped doing things the old way. They just know this is how you do it now. The sales manager doesn’t know about the promise someone in delivery made three months ago, because why would they? Marketing changes something that affects customer service. It looks perfectly reasonable from their side of the business. Nobody thinks to tell customer service until the phones start ringing and someone finally says, “Wait. What changed?”

None of these people are necessarily doing anything wrong. They just aren’t all standing in the same room anymore.

Then everybody says: “We have a communication problem.”

Maybe.

But that phrase has become the junk drawer of organizational problems. Put anything confusing in there and close it quickly.

Because “communicate better” sounds actionable while requiring almost no diagnosis.

Your Communication Problem Might Actually Be a Context Problem

I learned this one inside growing companies. Here’s a real life (but cleaned up for privacy) example of this:

When teams were small, they could get away with a lot. People talked. Questions moved quickly. Someone usually knew what was happening. Then the company grew. More developers. More roles. More layers. More people trying to make sense of work that had once been coordinated through conversations and memory.

Once the growing teams became more disciplined about actually capturing work, something interesting happened. Patterns appeared.

They could see where requests piled up. They could see where things slowed down. They could see recurring problems that had previously looked like isolated incidents.

The problems hadn’t suddenly appeared because the team documented them. They had finally made the system visible.

That kind of visibility matters when you’re scaling culture, because at eight people, culture can travel person to person. At 40, though, it has to travel through the way work actually happens.

How do we make decisions? Who gets included? What happens when priorities conflict? How does someone know what “good” looks like here? What can a manager decide without asking you? What happens when someone makes a reasonable decision and you would have chosen differently? Which customer problems deserve escalation? How do we disagree? What happens when someone drops a ball?

Those answers are your culture too.

Actually, once you start growing, they become a much larger part of it.

The Founder Becomes the Shortcut

Here’s where growing pains get particularly fun.

You hire because you need more capacity, then everybody starts asking you more questions.

Beautiful.

You now have more people specifically so you can personally answer questions for more people. At eight employees, founder access is efficient. At 40, not so much. Founder access can quickly become a workaround for missing clarity.

One manager asks you because she doesn’t know whether she has authority and another asks because last time she made the call herself, you reversed it. Someone else asks because the policy says one thing but everybody knows you make exceptions. Your oldest employees don’t ask because they know how you think, but your newest employees ask constantly because they don’t.

So the experienced people seem “more capable.”

Maybe they are, or maybe they have seven years of undocumented founder context stored in their heads.

That’s a very different problem.

Your growing business does not need 40 people who can read your mind. It needs a way to operate when you aren’t available to explain it.

Otherwise, you haven’t scaled your culture; You’ve just scaled access to you.

And there’s an upper limit on that particular operating model.

Spoiler alert: it’s you.

Unwritten Rules Get Expensive as You Grow

Every company has unwritten rules. At eight people, that isn’t automatically a problem because most people have enough shared history to understand how things really work, even when nobody has formally explained it. At 40, those same unwritten rules start creating completely different employee experiences.

One manager lets people work from home when a kid is sick, while another assumes they should take PTO. An employee who’s been there forever can spend $1,500 without asking because everyone trusts her judgment, while someone newer gets questioned over $75. One department has learned that customers come first no matter what. Another has been told protecting margin is the priority. One person knows that when you say “ASAP,” you mean today. The new guy assumes you mean sometime this week.

Nobody is necessarily behaving badly. They are making reasonable decisions based on the version of the company they’ve experienced. And once those versions start multiplying, so does the confusion. They are responding to the system they’ve experienced.

This is where leaders sometimes start getting frustrated and asking, “Why can’t people just use common sense?”

Whose common sense? Yours? The manager’s? The employee who started six weeks ago? The person who has been beside you since the company had four customers and a questionable logo?

Common sense depends heavily on context.

As the company grows, context becomes less evenly distributed. You can complain about that, or you can design for it.

Only one of those scales.

Scaling Culture Does Not Mean Preserving Everything

This is another place owners get stuck: They want to keep the culture.

I understand why. You built something people liked. Maybe the early team was incredibly close. Decisions were fast. People jumped across roles. Nobody hid behind job descriptions.

Why would you want to lose that? You definitely don’t. But preserving the culture does not mean preserving every behavior that existed when you were small.

Some behaviors were strengths and others were survival mechanisms. Everybody jumping into everything feels collaborative at eight people, but it gets insanely messy when that number multiplies.

I’ve seen countless founders talk about how decisions used to be responsive when they “first started,” but now, as they’ve grown… bottleneck.

Keeping everything informal can feel human at eight, but it’s decidedly less so with more people. Usually it means someone’s success may depend on whether they happen to know the right person.

You have to separate the principle from the practice.

Maybe what mattered was never “we don’t have processes.” Maybe what mattered was we don’t make people fight bureaucracy to help a customer.

Maybe what mattered wasn’t “everyone can do everything.” Maybe it was people take ownership instead of saying, “not my job.“

Maybe it wasn’t “anyone can walk into my office.” Maybe it was leaders are accessible and listen when something isn’t working.

Those things can survive growth, but the way you deliver them may need to change.

Scaling culture is not preserving the small-company version of your business forever. It’s preserving what mattered while redesigning how it works at the size you are now.

The Middle Gets Weird

Somewhere between founder-led and genuinely team-led, businesses hit an awkward middle. It looks a little like:

You’re too large to run everything through relationships, but you’re too small to have infrastructure for everything. Managers have titles, but their authority is fuzzy. Processes exist, except for the five situations where everybody knows you don’t follow them. Meetings multiply because people are trying to compensate for information they no longer absorb naturally. Departments start protecting their own work. Early employees become unofficial historians. Newer employees accidentally violate rules nobody told them existed.

And you start hearing phrases like:

“That’s how we’ve always done it.” “I thought they owned that.” “Nobody told us.” “I was waiting for approval.” “I didn’t know I could make that decision.” “Can you just ask Layne?”

Okay, ideally not that last one in your business, but you get the point.

This stage can make perfectly capable leaders wonder whether they hired the wrong people or somehow ruined a good company. Usually, neither is the most useful place to start. The business has just become more complex than the operating habits holding it together. And that is scaling strain.

So What Actually Needs to Change?

I’m going to take a slight detour from my regular tone and beg: Please DO NOT respond to growing pains by creating a 96-page employee handbook and six new standing meetings. You don’t need to bury 40 people under policies because things got messy.

Instead, look at where shared context used to do work that the system now needs to do.

Clarify decision rights.
Your managers can’t become managers if every meaningful decision still travels upward. Be clear about what they own, what requires input, and what truly needs escalation.

Make important work visible.
If people need three Slack messages and a meeting to figure out what is happening, the work isn’t visible enough. The point isn’t more tracking. The point is fewer interruptions and fewer surprises.

Turn assumptions into agreements.
How do teams communicate? What happens when priorities collide? When should someone escalate? What does ownership mean? Stop relying on people to infer rules from whichever employee trained them.

Give managers context, not just responsibility.
A title without context creates a messenger. They collect questions from their team, bring them to you, collect your answer, and carry it back. Congratulations. You invented expensive email.

Build their ability to see the situation, make a judgment, and own the outcome.

Decide what deserves to survive.
Your early culture probably contains things worth protecting. Protect them intentionally. But don’t keep a broken habit because somebody remembers it fondly from 2018.

Nostalgia is not an operating system.

Is This Normal Growing Pain or Scaling Strain?

Some friction during growth is normal. People are learning new roles. Teams are forming. Work is changing. You won’t eliminate every awkward moment, nor should you try.

But pay attention when the same problems keep returning:

Decisions repeatedly route back to you.
Managers have responsibility without real authority.
Meetings increase while clarity decreases.
Different teams follow different unwritten rules.
New employees take much longer to “get it” than expected.
Work stalls between departments.
Longtime employees become required translators for how things really work.
You keep adding people but don’t feel additional capacity.
Everyone is busy, yet important work keeps drifting.
Things move when you’re in the room and slow down when you’re not.

That’s more than a rough patch; it’s usually a sign that the business has outgrown the way it operates.

And that doesn’t mean you failed to build a good culture. In fact, a lot of the strain shows up because the culture did work. People trusted each other. They moved quickly. They took ownership. They solved problems without waiting for a rulebook. But those things were easier when everyone had the same context and could fill in the gaps for one another.

As the company grows, the culture that once emerged naturally needs more support. Not bureaucracy. Not corporate nonsense added just so the business looks more “grown up.” It needs enough clarity that people can keep making good decisions even when they aren’t sitting next to you or surrounded by the same eight people who built the early version of the company.

The best parts of a small business don’t have to disappear as it gets larger. Trust can scale. Ownership can scale. Humanity can scale. Fast decisions can scale.

They just stop happening accidentally.

Frequently Asked Questions

How do you maintain company culture as you grow?

You maintain company culture during growth by identifying which behaviors actually matter and building systems that support them at a larger scale. That includes clearer decision rights, manager expectations, communication paths, role clarity, and working agreements. Trying to preserve every informal small-team habit usually creates more confusion, not stronger culture.

How do you maintain company culture during rapid growth?

Start by finding where growth has made previously informal expectations unreliable. Look at how decisions move, how new employees learn, how managers lead, and how information crosses teams. Rapid growth increases organizational complexity, so culture needs clearer mechanisms for carrying context without making everything dependent on the founder.

What are the biggest risks to culture when scaling a business?

The biggest risks include inconsistent management, information silos, unclear authority, founder bottlenecks, conflicting team norms, and an increasing gap between longtime employees and newer hires. These issues often look interpersonal on the surface but are frequently symptoms of systems that haven’t kept pace with company growth.

Why does company culture change as a business grows?

Company culture changes because the conditions surrounding work change. Small teams rely heavily on proximity, shared history, informal conversations, and direct access to leadership. As headcount grows, those mechanisms reach fewer people. Without intentional systems replacing them, employees begin operating with different information, expectations, and interpretations.

Can you scale a business without losing its culture?

Yes, but you probably cannot scale it without changing how the culture is supported. The important question is not whether every habit survives. It’s whether the principles underneath those habits survive. A growing company may need more structure while still protecting trust, autonomy, responsiveness, and the human parts people valued when the business was small.

You Probably Don’t Need Your Old Culture Back

When owners tell me, “It just doesn’t feel like it used to,” I believe them. It usually doesn’t. How could it be the same? There are more people, more customers, more decisions, more history, and more risks and consequences.

To be clear: You’re asking a completely different business to operate like the old one. It might have the same name, same logo… but it is not the same place at all. And the fix to this isn’t just to recreate your first 8. It’s to figure out what those eight people could do naturally that people now need the company to support intentionally.

That’s the work. Once you can see where the strain actually lives, you can stop wondering why good people suddenly seem confused, why your managers keep coming back to you, or why adding employees somehow made you busier.

You built a bigger company. Now the way it works has to grow up with it.

If you’re not sure whether you’re experiencing normal growing pains or whether your systems have fallen behind your growth, start with the Scaling Strain Self-Assessment.

See where the strain is, then decide what actually needs to change.

You don’t need to become more corporate. You need a company that can keep being human without requiring you to personally hold every piece together.

-L