What Should a Founder Delegate First?

Why founders struggle to choose what to hand over

Most founders know, in the abstract, that they should be delegating more. What trips them up is not willingness but sequencing: they either try to hand over the wrong task first, such as a judgement-heavy client relationship, and get burned when it goes wrong, or they hold onto everything a little too tightly because no single task feels safe enough to let go of. Both outcomes come from the same missing piece: a clear way to decide which tasks are actually ready to be delegated, and in what order.

The starting point is to accept that not all tasks are equally delegable at the same point in time. A task can be delegated successfully once it is frequent enough to be worth training someone on, defined enough that success can be described, and low-risk enough that an early mistake will not seriously damage the business. Tasks that fail all three tests should stay with you for now, not forever, but for now.

The three-question filter

Before deciding whether to delegate a task, run it through three questions. First, frequency: does this happen often enough that training someone on it will pay back the time it takes to teach them? A task you do once a year is rarely worth delegating early, because the training cost outweighs the benefit. Second, definability: can you describe what a good outcome looks like clearly enough that someone else could judge whether they had achieved it, without asking you? Third, risk: if this is done imperfectly the first few times, what actually happens, and is that recoverable?

Tasks that score well on all three, frequent, definable, and recoverable if imperfect, are your first delegation candidates. Tasks that are frequent and definable but higher-risk, such as sending invoices to key clients, can usually be delegated with a review step built in for the first month or two. Tasks that are infrequent, hard to define, or high-risk, such as a major pricing decision or a delicate client negotiation, should stay with you until either the task itself becomes more routine or you have built enough trust with the person to hand over the judgement as well as the doing.

• Frequency: does this happen often enough to be worth training someone on?
• Definability: can you describe what good looks like without being present?
• Risk: is an early mistake recoverable, or genuinely damaging?
• Score each candidate task honestly against all three before choosing an order.

Start with recurring admin and process work

For almost every small business, the first genuinely safe delegation candidates sit in recurring administrative and process work: scheduling, data entry, expense processing, routine customer replies using existing templates, basic bookkeeping tasks, or diary management. These tasks tend to be frequent, easy to describe clearly, and forgiving of an early mistake, which makes them ideal for building the habits of delegation, both yours and the other person's, before anything higher-stakes is handed over.

This first stage is also where you learn what your own instructions are actually like in practice. If someone struggles with a task you thought was simple, it is very often because the instructions in your head were less complete than you assumed, not because the task or the person was wrong. Treat the first few delegations as a test of your documentation as much as a test of the person doing the work.

1. List every recurring task you do weekly or monthly that takes 30 minutes or more.
2. Mark which ones you could describe in a short written process without leaving anything out.
3. Pick two or three of the lowest-risk tasks from that list to hand over first.
4. Write the process down before you hand it over, not while explaining it verbally on the day.
5. Set a short review point, such as after the first two or three occurrences, to check quality.

Then move to defined outcomes with review points

Once the first round of tasks is running reliably without your daily involvement, the next tier is work that carries more consequence but is still definable: responding to standard customer queries without a template, managing a supplier relationship within agreed parameters, or handling routine parts of a client account. These are appropriate to delegate once you have confidence in the person's judgement from the first round, but they still benefit from a built-in review point, particularly in the first few weeks, so problems surface while they are small.

The mechanism that makes this stage work is a light but real check-in, not constant oversight. A short weekly conversation about what came up, what they were unsure about, and what they decided is usually enough to catch drift early without undermining the point of delegating in the first place, which is to free up your time, not to replace hands-on doing with hands-on watching.

What to keep for yourself, at least for now

Some categories of work are worth holding onto until either the business has grown enough structure around them or you have built deep trust with a specific person: strategic decisions about direction and pricing, sensitive people matters such as performance issues or disciplinary conversations, financial decisions with material consequences, and relationships with your most important clients or partners. These are not permanently off-limits to delegation, but they are the wrong place to start, because the cost of an early mistake is high and the learning curve for judgement calls like these is genuinely longer than for process tasks.

It is worth being explicit with yourself and, where relevant, with your team about which categories currently sit in this group, so that everyone understands the boundary is deliberate rather than a sign of distrust. As the business and the people in it mature, tasks move gradually from this group into the delegated group, but that should happen because trust and evidence have built up, not because you ran out of time to keep doing it yourself.

Delegating a judgement call before the doing has been proven is how good hires end up looking unreliable.

Delegating the doing versus delegating the decision

A common trap is delegating the tasks but not the decisions within them, which means the person is doing the work but still has to check with you at every fork in the road. This is not full delegation, and it does not free up meaningful time, because you are still the bottleneck for every judgement call, just at a smaller scale. Genuine delegation means the person can make the routine decisions inside a task without asking, and only escalates the exceptions you have agreed in advance.

The way to move from partial to full delegation is to write down, explicitly, what falls inside the person's authority and what needs to come to you. This does not need to be complicated: a short list of 'you decide' and 'ask me first' scenarios for each task is usually enough, and it can be adjusted as trust grows. Without this list, most people will default to asking about everything, which quietly recreates the bottleneck you were trying to remove.

Why delegation attempts fail, and how to recover

When a delegated task goes wrong, the instinctive response is often to take it back entirely and conclude that the person, or delegation itself, was not up to the job. In most cases the actual cause is one of three things: the instructions were incomplete, the task was too high-risk to be a first delegation, or there was no review point built in to catch the problem early. All three are fixable without abandoning the attempt.

The recovery path is usually to step back rather than take the task fully back: identify specifically what went wrong, tighten the instructions or add a review point, and hand the task back with the gap addressed. Taking a task back completely after one mistake teaches the person that mistakes are punished with removal of responsibility, which discourages exactly the kind of ownership you are trying to build.

A simple sequencing plan

If you are starting from close to zero delegation, a sensible order over the first two to three months looks roughly like this: recurring low-risk admin first, with written instructions and a short review point; then defined customer or supplier tasks with agreed parameters and a weekly check-in; then, only once both of those are running smoothly, a first small judgement call with a clear boundary on what still needs to come to you. Trying to compress this into weeks rather than months is, in Kayley's experience, the most common reason delegation attempts collapse.