Delegation

Handing over an outcome with the authority to decide how. Handing over tasks while keeping every decision is just queueing.

What is it?

Delegation is transferring responsibility for an outcome, along with the authority to make the decisions that outcome requires.

It is not assigning tasks. Assigning tasks while retaining every decision leaves you as the bottleneck with extra communication overhead.

Why does a founder care?

Because the founder becoming the bottleneck is the most reliable way a growing company stalls. Every decision routing through one person caps the company at that person's throughput.

And because people who are given tasks but no authority disengage. The good ones leave; the ones who stay stop thinking.

Example

Not delegation: 'Can you write the onboarding emails? Send them to me before they go out. Use the template I made. Check the wording with me first.'

The founder still makes every decision. They have added a person and a review cycle and removed none of their own work.

Delegation: 'You own activation this quarter. It is 8% and I would like it above 25%. Onboarding emails are probably part of it, but that is your call. Budget is $2,000. Check in with me weekly, and tell me if you need a decision only I can make.'

The difference: an outcome (activation above 25%), authority (it is your call), a constraint (budget), and a rhythm (weekly check-in).

Now the founder is not in the loop on wording. And crucially, the person can do something better than the founder would have — which is impossible under the first version.

The common mistake

First-time founders often delegate only the tasks they dislike, keeping everything interesting and everything important. That produces a team of assistants rather than a team of owners.

The second mistake: delegating without a check-in rhythm, then being surprised a month later. Delegation is not abdication — it needs a scheduled conversation, which is precisely what makes letting go safe.

The third: taking it back at the first mistake. If you reclaim ownership the first time something goes imperfectly, nobody will take real ownership again.

How it works

Step 1: Delegate an outcome, not a task list

'Activation above 25%' rather than 'write these emails'. The outcome is what makes ownership possible.

Step 2: State the authority explicitly

What can they decide alone? What needs you? Ambiguity here means everything comes back to you by default.

Step 3: Give the constraints

Budget, timeline, anything that must not change. Constraints enable autonomy rather than limiting it.

Step 4: Agree a check-in rhythm

Weekly or fortnightly. This is what makes delegation safe, and it is the step most often skipped.

Step 5: Let them do it differently

A different approach that works is a success. If only your method is acceptable, you have not delegated.

Step 6: Do not take it back at the first error

Coach through it. Reclaiming ownership once teaches everyone that ownership is not real.

When to use this

From your first hire, and increasingly as the company grows. By around twenty people, most of your job is this.

When not to use it

Do not delegate something you have never done yourself and cannot evaluate. And do not delegate the things only a founder can do — direction, key hires, culture.

Do this now

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