Delegation Readiness: Keep vs Hand Off Decision Tree
Why this matters
Owners get stuck because they delegate the wrong things and cling to the wrong things. They hand off a critical task to someone untrained and get burned, then conclude "I have to do everything myself." Or they keep doing low-value work out of habit while the real owner-level decisions go unmade. Good delegation is not "give away whatever you hate." It is a deliberate sort: what must stay with you, what should leave now, and what needs a step first. This decision tree walks that sort task by task.
Start here: list the task, then ask one filtering question
Take any task that currently lands on you and ask: does this genuinely require the owner, or does it just require someone competent? Most of what owners do falls into the second bucket. Be honest, because "only I can do this" is usually pride or habit, not truth.
Branch 1: Is this an owner-only decision?
Some things should never leave the owner's desk. Keep it if it is:
- A bet-the-company decision: large financial commitments, major hires, taking on debt, big strategic direction.
- A core relationship only you can hold: your largest accounts, key partnerships where you are the trust.
- Values and culture enforcement: what we will and will not do, who we let go.
If yes, keep it, but write down the boundary so the routine version can be handled by someone else. You sign the large bids; a manager can approve the small ones under a set limit.
If no, continue down the tree. Most tasks are not owner-only.
Branch 2: Is there someone who can do this at an acceptable standard today?
"Acceptable" is the key word. It does not mean "as well as you." It means good enough that the customer and the business are not harmed.
- If yes, hand it off now. This is your fastest win. Do not gold-plate the standard. If they will do it at eighty percent of your quality and that is fine for the task, delegate it today. The time you free up is worth more than the missing twenty percent.
- If no, go to Branch 3. Lack of a ready person is a training problem, not a reason to keep it forever.
Branch 3: Could someone do it with documentation or training?
Almost always yes. Ask: how big is the gap, and how often does the task recur?
- Frequent task, small gap: write the SOP, train one person, hand it off this month. High payoff.
- Frequent task, large gap: worth a real training investment. Pair them, document it, supervise, then release. This is how you build capacity.
- Rare task, large gap: maybe keep it for now and revisit. Training someone for a once-a-year task may cost more than just doing it. Judgment call.
The trap is letting "they would need training" become a permanent excuse. If the task recurs and matters, the training pays for itself fast.
Branch 4: Are you keeping it for a bad reason?
When you catch yourself unwilling to let go of a non-owner task, name the real reason:
- "It is faster if I just do it." True today, false over a year. The hundredth time someone else does it, you are way ahead. Eat the slow first ten.
- "They will not do it exactly my way." Correct, and usually fine. Delegate the outcome, not the keystrokes. Define what done looks like, not every move.
- "What if they mess it up?" Build a check, not a veto. Let them do it, review the result, coach the gaps. Mistakes on recoverable tasks are tuition, not disasters.
- "This is the part I actually enjoy." Legitimate, occasionally. But if your favorite task is also low-value, you are paying owner wages for hobby time.
How to hand off so it actually sticks
Dumping a task and walking away is not delegation; it is abandonment, and it fails. A clean handoff has four parts:
- The outcome: what done looks like, in plain terms.
- The boundaries: what they can decide alone and what needs to come back to you.
- The resources: the SOP, the access, the contacts they need.
- The check-in: how you will confirm it is going well, and for how long, before you fully release it.
Release the check-in over time. Heavy at first, then lighter, then gone. Hovering forever defeats the purpose.
The weekly habit
Once a week, look at your task list and ask of the biggest time-eater: "Is this still mine to do?" Delegation is not a one-time event. As your people grow, the line of what only-you-can-do should keep moving up the value chain. If it has not moved in a year, you stopped delegating.
References
- See related: Working On vs In the Business: A Decision Tree
- See related: Decision Authority Mapping: Who Owns What
- See related: Owner Time Audit: Where the Week Goes
- SBA guidance on delegation and management for growing small businesses