Delegation fails for a reason that has nothing to do with trust. It fails because the founder hands over a task and keeps the judgement, so every decision comes back anyway and the work is now slower than when they did it themselves.
You are not delegating tasks, you are delegating decisions
Handing someone your inbox is not delegation if you still decide what gets a reply. Handing someone the month-end close is not delegation if every reconciliation waits for your review.
The unit that actually transfers is a decision with a boundary around it. Reply to anything under this threshold without asking. Approve invoices up to this amount. Book travel within this budget. The boundary is what makes the handover real, and it is the part most founders skip.
Start with the work you can describe
A useful test before you hire: could you explain this job to a competent stranger in one page. If the answer is no, the problem is not that you lack a person, it is that the process only exists in your head.
Pick the areas where the steps are known and the judgement is bounded. Scheduling, bookkeeping, first-line support, reporting. Get those out, watch what that frees up, then move to the areas that need more judgement once the person has context.
If the process only exists in your head, you do not have a hiring problem yet. You have a documentation problem.
Replace approval with visibility
The instinct when you step back is to build an approval gate. Everything routes through you, so nothing goes wrong. In practice you become the bottleneck you were trying to remove, and the person you hired learns to wait rather than decide.
Visibility works better than approval. A shared board, a weekly written update, a dashboard you can read in two minutes. You see everything and stop nothing. When something is wrong you catch it in days, which is fast enough for almost every decision that is not legal or financial.
- Week one to four: they draft, you review everything, you explain the reasoning behind each edit.
- Week five to eight: they decide inside the boundary, you review a sample.
- Week nine onward: they own it, you read the weekly update and talk about exceptions.
Expect a dip, and plan for it
The first month is slower than doing it yourself. This is not a sign the hire is wrong. It is the cost of transferring context you accumulated over years into someone else in weeks.
Founders who quit delegation almost always quit during that dip. The ones who get through it are the ones who wrote things down as they went, so the second hire took two weeks instead of two months.
Keep the things only you can do
Letting go is not the same as absence. Strategy, key relationships, the final call on hiring and money. Those stay with you. Everything downstream of them is a candidate for someone else, and the point of the exercise is to buy yourself the time to do the first list properly.
