Delegation is the single most important skill for business owners trying to grow past their own bandwidth. Get it right and the business compounds; get it wrong and you remain the bottleneck of everything. Most owners think they delegate. Most don't - they assign work while keeping the decisions.

Four principles

1. Delegate the outcome, not the steps

The most common delegation mistake. The owner hands over the work but keeps the thinking - so every step requires the owner's judgment, decisions, and approval. The delegate becomes an executor, not an owner. The founder ends up doing more work, not less.

Real delegation hands over both:

  • The outcome - what success looks like
  • The decisions - including the judgment calls along the way

The delegate brings their own approach. Some of their decisions will surprise you. If the outcomes are good, the differences don't matter.

2. Show what "done well" looks like

Without examples, delegates guess at quality - and they usually guess wrong, often lower than your standard. Showing examples of past work that worked anchors them to the right bar.

Concretely:

  • Share 2-3 past examples of strong output
  • Explain what makes them strong
  • Note the common failure modes you want them to avoid

3. Set cadence, not approvals

Approvals before action defeat delegation. The delegate is just executing your decisions; nothing has actually been handed off.

Instead, set a check-in cadence:

  • Weekly review of work completed
  • Monthly review of metrics
  • Quarterly review of approach

Between cadence points, the delegate decides and acts. You review outcomes, not approve actions.

4. Don't take work back

Taking work back signals the delegation was conditional. The delegate learns not to fully own the work; they learn to do enough to keep you from taking it back.

Better responses when something goes wrong:

  • Fix the success criteria if they were unclear
  • Provide more examples if the bar was unclear
  • Reassign if the person isn't right for the work
  • Coach if the gap is skill

Almost never: take it back.

Delegation maturity model

A useful progression for any specific responsibility:

  1. I do it - the founder does the work personally
  2. I do it together with them - the delegate learns by working alongside
  3. They do it; I review - the delegate owns it; founder catches errors
  4. They do it; I trust - the delegate owns it; founder only sees outcomes

Most delegation gets stuck between steps 3 and 4. The founder keeps reviewing because reviewing feels safe. Moving to step 4 requires accepting that some mistakes will happen on the delegate's watch - and that's OK.

What to delegate first

Useful priorities:

  • Work the founder is doing because they always have, not because they're uniquely good at it
  • Work the founder is least skilled at - someone else will do it better
  • Work that doesn't require the founder's judgment - process, execution, coordination
  • Work that's holding up other work - bottleneck activities

Last to delegate: vision, strategy, key relationships, decisions with reputational weight.

Common mistakes

1. Delegating tasks instead of outcomes

Already covered. The biggest mistake.

2. Hiring before delegating clearly

Bringing in a senior person without clear delegation means an expensive person doing what the founder vaguely directs.

3. Taking work back at the first mistake

Trains the team that delegation is conditional. They stop fully owning the work.

4. Delegating too little, too late

Most founders delegate later than they should. The pain threshold for delegating is much higher than the actual threshold should be.

Related concepts