“It’s faster to just do it myself” is the sentence after which a small-business owner hits a ceiling at 8–10 people and stops growing. Not because they don’t want to delegate, but because every attempt ends in rework.
The problem is almost never the people. It’s that delegation is treated as a single act — say it and forget it — when it’s a system with four parts: what you hand over, to whom, how you phrase it, and how you accept it.
Why “doing it yourself” is a trap
The arithmetic is simple. A task that takes you an hour takes an employee three — the first couple of times. Plus half an hour explaining and half an hour reviewing.
The first time, you lose three hours. The fifth time, they do it in an hour and a half without you. By the tenth, you don’t think about that task at all.
Refusing to delegate is choosing to save three hours now while losing an hour every week thereafter. Within a quarter the gap is already tens of hours.
There’s a second, less obvious cost: an employee nobody delegates to doesn’t grow, and leaves. Not from workload — from stagnation.
Step 1. Work out what to hand over at all
Not everything. List your tasks from last week and sort them into four groups:
- Always keep — strategy, negotiating large contracts, hiring key people, resolving conflicts, giving feedback.
- Hand over immediately — routine with no decisions attached: reports, paperwork, standard replies, mailings. Mistakes are cheap here, which makes it the best starting point.
- Hand over gradually — some client relationships, running projects, hiring for regular roles. Requires transferring context, but pays back the most.
- Stop doing entirely — things done out of habit that nobody needs. Part of the list usually lands here, and it’s the fastest win.
Start with the second group: cheap mistakes and quick results. The common error is starting with the most painful item.
Step 2. Set the level of autonomy
The main cause of rework: manager and employee understood differently how much freedom was being given. One meant “do it however you see fit”, the other heard “bring me options to pick from”.
State the level explicitly. There are five:
- Do exactly as instructed. For newcomers and for critical work.
- Investigate and propose options; I decide. They research, you decide.
- Decide yourself, but check before launch. Their responsibility, your veto.
- Decide, do it, then tell me. The default mode for an experienced person.
- Decide, do it, no report needed. Full ownership of an area.
The level rises with trust and per task, not by job title: the same person can be at level 5 in their own area and level 2 in a new one.
One line in the assignment — “this is level 3, decide yourself but show me before it goes to the client” — removes most of the rework.
Step 3. Phrase the assignment completely
An assignment that doesn’t come back for rework contains five elements:
- What’s needed — the result, not the process. “An estimate for the client”, not “crunch some numbers”.
- Why — context. Knowing the goal, they’ll make the right calls in the places you didn’t anticipate.
- By when — a date, not “soon”.
- Definition of done — how you’d both know it’s good.
- The autonomy level — from step 2.
Compare.
Bad: “Have a look at what’s going on with the client report.”
Good: “Prepare the client report for project A covering July. It’s for Thursday’s meeting — they’ll be deciding on renewal. Have it by Wednesday, show me before sending. Done means: traffic, leads and cost-per-lead figures, plus a one-paragraph conclusion.”
The second takes 30 seconds to write and saves two rounds of revisions.
A trick for checking comprehension: ask them to restate in their own words what needs doing. Not “does that make sense?” — that always gets a yes. A restatement exposes the gap immediately rather than on the due date.
Step 4. Don’t lose the assignment
A separate failure mode: the assignment was made in conversation or in a chat, and afterwards both sides remember it differently — or not at all.
The rule: every delegated item exists in writing, in one place. Not across three chats, not in email, not in a notebook. Otherwise a week later “but I asked you to” becomes an argument without evidence.
If your assignments are born in conversation, this rule is easier to automate than to enforce by willpower: the bot recognises tasks in chats and turns them into assignments with an owner and a date. “But I asked you to” stops being a question of memory.
Step 5. Check in the middle, not at the end
The classic mistake: hand over a week-long task and remember it on Friday evening. If the person went the wrong way, you find out when there’s no time left to fix it.
On any task longer than two days, set a checkpoint at roughly a third of the way: not a report, a five-minute direction check. Correcting is cheap at that stage.
Don’t confuse this with hourly supervision, though: constant “how’s it going?” backfires — people stop taking ownership because they sense the decision is yours anyway.
Step 6. Handle mistakes properly
The first rounds of rework are inevitable. How you respond decides whether delegation continues to work.
Works: unpack the cause together. What was unclear? What information was missing? What stopped you from asking? Nearly always the defect turns out to be in the briefing, not the execution.
Doesn’t work: silently redoing it yourself. They never learn what was wrong and repeat it next time. And you further convince yourself it’s faster alone.
Kills delegation: taking the task back after the first mistake. After that, nobody volunteers for it again.
The one-mistake rule: the same mistake twice is a system defect. That calls for a checklist, a template or a written standard — not another conversation.
When it still feels faster to do it yourself
Three common reasons and what to do about them.
“Nobody will do it as well.” Define “well”. Often it turns out 80% of your quality is enough, and the remaining 20% is personal perfectionism the client isn’t paying for.
“Explaining takes longer than doing.” True for a one-off. For anything recurring, do the maths across a quarter. You explain once and save every week.
“Everyone’s already swamped.” Possibly true. Look at actual workload rather than the feeling: usually two people are buried and the rest are idle — which is visible when tasks and deadlines live in one place instead of in people’s heads.
Bottom line
Delegation doesn’t break on people, it breaks on the briefing: what exactly is needed, by when, by what standard, and how much freedom the person has. All four are fixed by one habit — phrasing the assignment fully and in writing.
Start small: take three routine tasks from your week and hand them over with an explicit autonomy level and definition of done. In a month you’ll have a day back.
If assignments in your team are born in chats, Gosudarynya pulls them out and tracks the dates, so “but I asked you to” turns into a task with a deadline. 7 days free, no card. How to put the rules in writing is in the team working agreement.