Growth Is a Test of Everything You Built

By Ty Sutherland

When a team is small, things work in ways that are hard to explain. Communication is fast because everyone is in the same room or the same Slack channel. Trust is high because people know each other well. Quality stays consistent because a few key people touch everything. Problems get solved before they become disasters because someone always notices.

Then headcount doubles. Or triples. And suddenly the things that used to happen automatically stop happening. Meetings get slower. Decisions take longer. New people don’t quite get the culture. The quality that used to be a given now has to be managed. And somewhere in the middle of all that growth, you realize you’ve been so focused on hiring that you forgot to think about what you were building.

This is the scaling problem. It’s not unique to startups or tech companies. It happens to any team that grows faster than its systems, its communication, and its culture can keep up with. And it’s almost always preventable—if you know what to protect before you start adding people.

Get Clear on What Actually Made It Work

Before you hire the next person, take an honest inventory of what’s working and why. Most managers skip this step because growth feels urgent. That’s exactly why so many teams lose their identity during a scale-up.

Ask yourself a few direct questions:

• What does this team do better than anyone else we know of?
• What behaviors make that possible—and are those behaviors written down anywhere?
• What do new team members consistently say surprised them in a good way?
• What would break first if we doubled in size tomorrow?

The answers to these questions are your scaling blueprint. They tell you what to codify, what to protect, and what to reinforce as you grow. If you can’t answer them clearly, spend a week observing your team before you post another job listing.

The goal isn’t to freeze the team in amber. It’s to understand what the core of your culture actually is—so you can scale around it rather than through it.

Document Before You Delegate

Small teams run on shared context. Everyone knows the unwritten rules because they watched them form. New people don’t have that context. They’re joining a story that’s already halfway through, and without documentation, they spend the first several months making mistakes that feel avoidable to everyone but them.

The fix is simple but takes discipline: write things down before you need to explain them for the third time.

That includes:

• How decisions get made. Who needs to be consulted? What can individuals decide on their own? What requires manager sign-off?
• How work gets reviewed. What does “good enough” look like versus “excellent”? What are the non-negotiables on quality?
• How the team communicates. What goes in Slack versus email versus a meeting? What’s the expected response time?
• What the team values. Not a mission statement—specific behaviors that are rewarded, and specific things that are considered off-brand.

You don’t need a 50-page culture handbook. You need a living document that new people can read in 20 minutes and walk away from with a clear picture of how things work here. Start with one page and add to it every time you catch yourself explaining the same thing twice.

Hire for Culture Fit Without Hiring Clones

One of the most common scaling mistakes is hiring people who are exactly like the people already on the team. It feels safe. It feels like you’re protecting culture. It’s actually how teams become fragile.

Culture fit doesn’t mean personality match. It means someone who shares the team’s values and working style—but may bring different skills, backgrounds, perspectives, and ways of thinking. That diversity is what makes a team capable of solving harder problems as it grows.

In practice, this means your interview process needs to get specific. Instead of asking “do you think this person would fit in here,” ask:

• Does this person demonstrate the behaviors we’ve identified as core to how we work?
• Have they navigated situations that required the kind of judgment we value?
• Can they articulate how they’d approach a problem in a way that’s consistent with how we think—even if their answer is different from ours?

The goal is to add people who make the team better without changing what makes the team itself. That’s a harder bar to hire to, but it’s worth the extra screening rounds.

Build Communication Structures That Scale

On a five-person team, you can run everything through one standup and a weekly all-hands. On a fifteen-person team, that structure collapses. People start missing context. Decisions happen in side conversations. The team fragments into informal subgroups that don’t always share information.

Communication structures need to grow in proportion to the team. That doesn’t mean more meetings—it means more intentional meetings.

A few principles that hold up at most sizes:

• Separate operational communication from strategic communication. Daily standups and project check-ins are for execution. Weekly or biweekly team meetings are for direction, priorities, and bigger-picture context. Don’t mix them—it makes both worse.
• Write decisions down and make them findable. Every significant decision should be documented with the reasoning behind it. This is especially important as the team grows, because new people will ask “why do we do it this way” and someone needs to be able to point to an answer.
• Create explicit handoff protocols. On a small team, handoffs happen naturally through proximity. On a larger team, things fall through the cracks between roles. Define who owns what at each stage of your key workflows—and revisit those definitions every quarter.

The teams that scale communication well are the ones that err toward over-communication in writing and under-communication in synchronous meetings. Written communication scales. Real-time meetings don’t.

Protect the Manager-to-Team Ratio

Nothing degrades team quality faster than stretching managers too thin. The generally accepted ratio for a manager running a healthy, functional team is somewhere between five and eight direct reports—depending on how senior they are, how complex the work is, and how much coaching they need to do.

When that ratio slips to twelve or fifteen because headcount grew faster than the management layer, everything suffers. One-on-ones become perfunctory. Feedback slows down. Performance issues go unaddressed because there isn’t time to address them. The team feels like it’s running without anyone actually watching.

As you scale, plan your management structure before you need it. The moment you see a manager getting pulled into more than eight direct reports, it’s time to either promote a senior individual contributor into a lead role or hire a manager. Waiting until it’s visibly broken costs you six months of drift that’s hard to recover from.

If you’re the manager doing the scaling yourself, be honest about your own bandwidth. You cannot run a growing team and onboard every new hire and fix every broken process simultaneously. Something will give, and it’s usually the thing you haven’t explicitly protected.

Onboarding Is Culture Transmission—Take It Seriously

New employees don’t absorb culture by osmosis. They absorb it through what they see rewarded, what they hear people talk about, and what they’re explicitly taught in their first few weeks.

A sloppy onboarding process doesn’t just slow down time-to-productivity. It actively dilutes culture. New people fill in the gaps with assumptions from their last job, which may be nothing like how you work. After a few waves of growth, the team starts to feel incoherent—like a mix of different companies’ cultures, none of them quite dominant.

A good onboarding process for a scaling team includes:

• A structured first two weeks. Not just “here’s your laptop and your Slack.” A deliberate schedule of who they meet, what they read, and what small wins they should aim for before day 15.
• A clear explanation of how work gets done here. Share the documentation you’ve already written. Walk them through your decision-making norms, your communication expectations, and your quality standards.
• A buddy or onboarding partner. Someone who isn’t their direct manager and can answer the questions new hires are too nervous to ask their boss. This is especially valuable for culture transmission because it’s informal and honest.
• A 30-60-90 day check-in structure. Regular touchpoints where you ask not just “how’s the work going” but “what have you learned about how we operate here that surprised you.” The surprises are often the signals you need.

Watch for the Warning Signs Before They Become Crises

Scaling problems rarely arrive as sudden catastrophes. They creep in as small signals that are easy to explain away when you’re busy.

Watch for:

• Decisions that used to happen in minutes now taking days or requiring escalation
• New team members consistently making the same categories of mistakes
• Long-tenured employees starting to disengage or express frustration about “how things used to be”
• Customers or stakeholders noticing inconsistency in output quality
• Informal sub-groups forming with their own norms that differ from the team’s

Any one of these is worth investigating. More than two at the same time means you’ve already got a scaling problem in progress—and the sooner you name it, the easier it is to fix.

Keep Checking In on the Intangibles

The things that made a small team great are often intangible: a sense of shared ownership, the feeling that everyone’s voice matters, the energy that comes from being part of something that moves fast and does good work. Those things are fragile. They require active maintenance as teams grow.

This means building in regular reflection—not just retrospectives on projects, but honest conversations about how the team itself is doing. Are people still energized? Do they feel like they understand where the team is going? Do they trust each other? Do they trust you?

A quarterly pulse check—even just three or four questions in a short anonymous survey—gives you data on the intangibles before they become visible in output metrics. The best managers treat team health as something to measure, not just something to sense.

Growth Should Make the Team Better, Not Just Bigger

The goal of scaling isn’t to add headcount. It’s to increase what the team can accomplish—while keeping the quality, culture, and cohesion that made it worth scaling in the first place.

That requires intentionality at every stage. Document before you delegate. Hire for culture fit without hiring clones. Build communication systems before they’re needed. Protect your managers. Onboard with care. And keep checking in on the things that are hardest to measure.

Teams that scale well don’t happen by accident. They’re built by managers who understand that growth is a test of everything they’ve already built—and who plan accordingly.