The Founder’s Guide to Better Delegation

Most founders know they should delegate more. Many have tried. A task gets handed to a capable person, comes back not quite right, and quietly returns to the founder’s list. After a few rounds of this, the founder concludes that it is faster to do the work themselves. In the short term they are right. Over a year, that decision caps the size of the company at the size of one person’s calendar.

In our experience, delegation rarely fails because founders are unwilling to let go. It fails because what is being handed over has never been defined. The task is clear, but the outcome, the boundaries and the decision rights are not. This guide is a practical way to fix that.

Start with a decision audit, not a task list

Before deciding what to delegate, spend two weeks writing down every decision you make that takes more than a couple of minutes. Note who brought it to you, how long it waited, and whether anyone else could reasonably have made it. Founders are usually surprised by two things: how many decisions arrive by default rather than by design, and how few of them truly require the founder’s judgment.

Sort the list into three groups. Decisions only you should make, such as fundraising, the most senior hires and the company’s overall direction. Decisions someone else could make with clear guidance. And decisions that should not exist at all, often approvals that once mattered and now simply slow things down.

Delegate outcomes, not activities

“Can you update the pricing page?” is an activity. “Make sure prospects understand our three plans well enough that sales calls stop starting with basic questions” is an outcome. The second version tells the person what good looks like, invites better ideas than yours, and makes it obvious when the work is done.

When you hand over an outcome, describe four things in writing: the result you want, why it matters now, the constraints that cannot move, and the date you will review progress together. That short note does more to prevent rework than any amount of checking in afterwards.

Be explicit about decision rights

A common source of frustration is ambiguity about who decides. A useful habit is to label each delegated area with one of four levels:

• Recommend: they research and propose; you decide.
• Decide and inform: they decide and tell you afterwards.
• Decide within limits: they decide inside a budget, timeline or policy you have agreed.
• Own: they decide, and you hear about it in the regular review.

Most areas should move up these levels over time. Saying which level applies today removes a surprising amount of tension, because people stop guessing whether they are allowed to act.

Expect a dip, then measure the right thing

The first few handovers will not be done exactly the way you would have done them. That is the cost of building capability in the team. Resist the urge to judge the work against your own approach. Judge it against the outcome you described. If the outcome was met, the different route is fine. If it was not, the gap is usually in the brief, which is a useful thing to learn.

The question is not whether they did it your way. The question is whether the outcome was met.

Protect the time you free up

Delegation only changes the business if the hours it frees go somewhere deliberate. Decide in advance what the reclaimed time is for, whether that is product direction, key customers, investor relationships or simply thinking time, and put it in the calendar. Otherwise new interruptions will fill the gap within two weeks.

Better delegation is less about personality and more about structure. Clear outcomes, explicit decision rights and a regular review create the conditions for people to take real ownership. Once that happens, founders often find they have not lost control at all. They have simply moved it to where it does the most good.

Sample article written for this demonstration website. 668 words.