Organization Design

The Founder-to-manager Transition and the First Fifty People

Work out, in arithmetic rather than in feelings, the point at which the founder stops being the fastest route to a decision and becomes the queue — and what specifically has to be handed over first.

  • Advanced
  • 14 min total
  • 15 chapters

What decision this helps you make: When to add a management layer, which classes of decision to transfer first, and whether the person who should run the company at fifty people is the person who got it to fifteen.

What this topic is

The founder-to-manager transition is the change from doing the work and making every call to designing a system that makes calls without you. It is forced by arithmetic, not by preference: communication paths grow with the square of headcount, a founder's week does not grow at all, and somewhere between roughly fifteen and fifty people the founder stops being the fastest route to a decision and becomes the slowest.

Why it matters

This is the stage at which most companies either build an organisation or install a permanent ceiling. The ceiling does not announce itself as a ceiling — it shows up as a founder working seventy hours, good people leaving quietly, decisions taking days that used to take minutes, and a persistent sense that everything would be fine if the team were just a bit more senior. All four are symptoms of the same structural fact, and none of them is a people problem.

Who should learn it

Founders and owner-managers between roughly ten and eighty people; first-time chief executives; and anyone joining a founder-led company as its first real operating leader who needs to understand what is about to be asked of them.

What you will understand

  • The arithmetic that forces the transition, and how to compute where your company is on it
  • What to hand over first, in what order, and what a founder should genuinely keep
  • What the research says about founders being replaced — including the uncomfortable finding about success
  • Why the employment model you choose in the first fifty hires is expensive to change later

Prerequisites

Common misconception

"I will delegate once I find people good enough." The sequence is backwards and the belief is self-confirming: a company where every decision routes through the founder does not attract or retain people who are used to making decisions, so the talent never arrives to justify the delegation. It is also the wrong diagnosis. The constraint is not the quality of your people; it is that pairwise communication paths grow with the square of headcount while your week stays at the same length. Brooks made the point in 1975 about software teams and it generalises exactly.[4] You do not delegate because your people became good enough. You delegate because the arithmetic stopped working, and then you find out who is good enough.