Scaling the organisation

Structure is a communication tool. You add it when coordination starts costing more than the work — and not one hire before.

What is it?

Scaling the organisation means adding structure — managers, teams, defined ownership — so that people can act without waiting for you.

The unit of the problem is not headcount. It is the number of connections between people, which grows far faster than the headcount does.

Why does a founder care?

Because coordination cost is what actually breaks growing companies. Ten people have 45 possible pairs; fifty people have 1,225. The work does not get harder — knowing who is doing it does.

Structure is how you cap that. Its purpose is to reduce the number of people any one person has to coordinate with.

Example

A team goes from 8 to 22 in a year with no managers, because flat feels faster.

By month nine the founder is in 30 hours of meetings a week, two people have unknowingly built the same feature, and nobody can say who decides the roadmap. Three good people leave — not because of pay, but because nothing they did seemed to conclude.

The common mistake

Promoting your best individual contributor into management as a reward. Management is a different job, not a senior version of the same one, and the usual result is one worse manager and one lost great engineer.

How it works

Step 1: Add structure at the pain, not on a schedule

The signal is decisions waiting on you and duplicated work — not reaching a headcount number.

Step 2: Make ownership explicit

Every important area has one name against it. Shared ownership of something important means nobody owns it.

Step 3: Promote deliberately

Ask whether the person wants to manage and is good with people. Offer a senior IC path so management is not the only way up.

Step 4: Write down how decisions are made

Who decides, who is consulted, who is told. Most organisational friction is an undocumented decision right.

Step 5: Keep a rhythm

A weekly team beat and a quarterly planning beat replace a hundred ad-hoc check-ins.

When to use this

When decisions are queueing on you, work is being duplicated, or people cannot say who owns something.

When not to use it

Under about ten people. Structure added early costs speed and buys nothing — everyone can still see what everyone else is doing.

Do this now

• Write one name against every important area
• Note which decisions are currently queueing on you
• Decide whether anyone needs a senior IC path rather than a management path

Apply this to your own startup in My Full Journey (free account).