What to hand over first

Most owners already know they should delegate. The question that stalls them is narrower: what goes first?

The usual answer is whatever you hate most. That feels right and it is usually wrong. The task you hate is often the one with the least structure, the most judgment, and the fewest people who could pick it up. Hand that over first and you spend three weeks explaining it, get it back half done, and conclude that delegating does not work for your business.

Pick the work that repeats

The first handover should be the most boring thing on your list. Something that happens every week or every month, in the same order, with a right answer at the end. Payroll. Supplier invoices. Chasing the receipts your bookkeeper asks for at the same point every month.

Boring work is a good first candidate for three reasons. It is easy to write down, so the handover survives the person who takes it. It has an obvious pass or fail, so you find out quickly whether it is actually being done. And because it repeats, the time you spend explaining it is paid back within a month rather than never.

Three questions

For any task on your list, ask:

1. Does it repeat on a schedule? If it happens once, delegating it costs more than doing it.
2. Is there a right answer? Work that ends in a number, a filing, or a payment can be checked. Work that ends in a judgment call needs you for longer.
3. Does anything stall when it is late? If a delay blocks other work, or other people, that is where handing over buys you the most.

Anything scoring three out of three should go first. That is usually the finance and admin cycle, which is why it is where we normally start with a new client.

Why the first one should be dull on purpose

The first handover is not really about the task. It is a test of whether the system around it works: whether the process got written down, whether somebody other than the person doing it could run it, whether you can see it was done without asking.

If that holds on something boring, it will hold on something harder. If it does not hold, you have learned that cheaply, on work where a mistake costs a day rather than a client.

What thirty days should look like

You should be able to say, without checking, that the thing happened. There should be a written version of it that someone new could follow. When the person doing it is away, somebody else should be able to run it from what is written down. And your involvement should be a short review rather than a set of instructions.

If all four are true after a month, hand over the next thing. If any one of them is not, fix that before adding more. Nobody starts with everything, and the ones who try are usually the ones who end up taking it all back.