The 14 Pillars/Compounding
Pillar 14

Lead

The last thing a founder has to scale is the founder.

You are here ifThe company runs well when you are in the room and drifts when you are not.
Establish the field of direction, orient the compass, then settle on a clear heading.

This is the pillar the other thirteen depend on. Systems get built and then bypassed, decision rights get assigned and then overruled, hires get made and then micromanaged — all by a founder who genuinely intended otherwise, because the behaviour that built the company is the behaviour that now limits it.

The shift is from being the person who does the work to being the person who designs the system that does it. It is an identity change before it is an operational one, and that is why it is the hardest.

How this goes wrong

Delegating the task and retaining the decision

The work moves to someone else, the authority does not. The team learns that their judgment is provisional and stops exercising it. Escalations rise, and the founder concludes the team is not ready — having built the conditions that guarantee it.

Answer these honestly

  1. What are you still doing that someone else should own, and what is the real reason you have not handed it over?
  2. When did you last overturn a decision that was inside someone else's authority?
  3. If you took a month off, what would break — and is that a system problem or an identity one?
  4. What do you do that is genuinely irreplaceable, as opposed to merely unpleasant to hand over?
  5. Does your team bring you decisions, or recommendations?

The method

01

Audit where your hours go

Two weeks of honest logging. Sort into: only I can do this, I prefer to do this, I have not handed this over. The second and third categories are the work.

02

Transfer authority with the task

Delegation without decision rights is supervision. State the boundary within which the owner decides without asking.

03

Hold the line on the system

The first time you bypass your own process under pressure, the process becomes advisory. Consistency here is the whole mechanism.

04

Design the culture explicitly

How disagreement works, how decisions get made, what gets someone removed. Unwritten culture defaults to whatever the founder tolerates on a bad week.

What installed looks like

  • ✓The team brings recommendations, not questions
  • ✓Decisions inside someone's authority are not overturned
  • ✓A two-week absence is invisible in output and in morale
  • ✓Your calendar reflects capital allocation and design, not firefighting

The three most common mistakes

Confusing being needed with being useful

A founder who is constantly needed has built a company that cannot function — and often quietly prefers it that way.

Delegating outcomes without authority

Accountability without decision rights is not delegation. It is blame with extra steps.

Reclaiming under pressure

Taking the work back during a crisis undoes six months of transfer in an afternoon.

The number that says it is workingPercentage of your week spent on work only you can do. If it is below half, the constraint is still you.
Free live class

Knowing the pillar is not the same as knowing it is yours.

Ninety minutes to run the diagnostic on your own numbers and leave with the binding constraint named plus the pricing architecture and the 90-day cadence that follow from it.

Save my seat — free →