Why Companies Slow Down After Scaling

Because the number of people who must agree before work ships grew alongside headcount. It feels sudden because it crosses a threshold rather than accumulating visibly. Count the approvers on a typical change today against a year ago: that number, not team size, is what changed.

Organisational debt accumulates without anyone deciding

Most of the drag in a scaling company comes from things that were individually reasonable when introduced and were never removed.

• A weekly sync created for a launch that shipped two years ago
• An approval step added after one bad incident, applied to every change since
• A role created to bridge two teams that have since merged
• A review process designed for a team of five, still running at forty

None of it is anyone's fault, which is exactly why it survives. Nobody defends it and nobody removes it. The practical fix is a recurring audit with a bias toward deletion: for each ritual and approval, name the problem it solves today. Not the problem it was created for.

Reorganise one boundary at a time

The instinct when a structure stops working is to redraw it comprehensively. Large simultaneous reorganisations reset every working relationship at once, and the recovery period routinely costs more than the new structure saves.

Change one boundary, let it settle for a quarter, then assess. This is slower on a slide and faster in reality, and it has the additional benefit of producing evidence about whether the change helped, which a comprehensive reorganisation never does because everything moved at once.

Early employees disengage for structural reasons

The usual explanation is compensation, and it is usually wrong. Early employees disengage because the job they signed up for gets replaced by one they did not choose.

Someone who joined to build things at speed finds themselves in planning meetings and reviewing other people's work. That is a different job. Sometimes it is a job they want, and sometimes it is offered as a promotion because the org has no other way to grow their scope.

The avoided conversation is whether the person wants to keep doing the work or start managing it. Asking directly, and building a path where the first answer is legitimate and well paid, retains more early employees than any equity refresh. Though the refresh matters too: a grant that fully vests with no successor in sight converts a motivated employee into a rational job seeker on a predictable schedule.

Hire for twelve months, select for eighteen

Hiring for the team you will need in eighteen months is common advice and produces a specific failure: capability you cannot yet use and often cannot retain, because the person spends the interim underemployed and leaves before the role they were hired for exists.

Hire for the work in front of you. Select, among candidates who can do that work, for the ones who could plausibly grow into the larger version. That gets you productivity now and optionality later, without paying for a future that may not arrive in the shape you planned.

Common questions

How do I reorganise without disrupting velocity?

Change one boundary at a time and let it settle before the next. Large simultaneous reorganisations reset every working relationship at once, and the recovery cost usually exceeds whatever the new structure was meant to save. Sequenced changes are slower on paper and faster in practice.

How do I identify organisational debt in my team structure?

Look for roles and rituals that exist because of a problem that no longer exists. A weekly sync created for a launch two years ago, an approval added after one bad incident, a role created to bridge two teams that have since merged. None of it is anyone’s fault and all of it compounds.

How do I keep founders and early employees engaged through scaling?

Give them scope that grows in a direction they want, and be honest when that direction is not management. Early employees usually disengage because the job they loved was replaced by a job they did not choose, not because of money. The conversation people avoid is whether they want to keep doing the work or start managing it.

How do I structure bonus and equity in a scaling startup?

Refresh equity before it becomes a retention conversation, and keep bonus tied to outcomes people can actually influence. The common failure is a grant that fully vests with no refresh in sight, which turns a motivated employee into a rational job seeker on a predictable schedule.

Should I hire a traditional HR team or build people ops differently?

Bring in compliance and payroll competence early because the downside is legal, and be slower to import performance and levelling machinery from large companies. Those systems assume a stable org, and applying them to a company still discovering its shape freezes the shape prematurely.

Should I hire for my current team or the team I’ll need in 18 months?

Hire for the next twelve months and select for people who can grow into the eighteen-month version. Hiring purely for a future state buys capability you cannot use yet and often cannot retain, since people hired for a job that does not exist yet spend the interim underemployed.

Why is my company suddenly slow after scaling?

Because the number of people who must agree before something ships grew with headcount. The slowdown feels sudden because it crosses a threshold rather than accumulating visibly. Count approvers on a typical change now against a year ago, and the cause is usually obvious.