How do you scale a team rapidly without breaking it?

Question

Accepted Answer

Scaling fast is dangerous because **you can dilute culture and break communication faster than you add capacity**. The goal is to grow *capability*, not just headcount — and to protect what made the team work.

## Principles for scaling well

```text
1. HIRE AHEAD OF NEED, NOT IN PANIC — rushed hiring lowers the bar
2. PRESERVE CULTURE — onboard deliberately; over-communicate values
3. SPLIT BEFORE IT HURTS — past ~8–10, split into focused sub-teams
4. GROW LEADERS INTERNALLY — you need leads/managers faster than you think
5. WRITE THINGS DOWN — tribal knowledge doesn't survive headcount doubling
6. ONBOARDING THAT SCALES — a buddy + a clear 30/60/90, not osmosis
```

## The communication problem

Communication paths grow roughly with the square of team size. A team of 5 has 10 links; a team of 12 has 66. This is *why* teams must split — not because people dislike each other.

## Pitfalls

- **Lowering the hiring bar** to hit a headcount number.
- **No onboarding plan**, so new hires flounder and dilute output for months.
- **Promoting your best IC to lead** with zero support and watching both roles suffer.
- **Adding people to a late project** (Brooks's Law) and slowing it down.

## Why it matters

Many teams scale headcount and lose velocity — more people producing less, because coordination overhead swamped the added capacity.

Scaling well means the team is stronger at 20 than it was at 8: clearer ownership, real leaders, and a culture that survived growth instead of being washed out by it.