You’ve tried delegating before.
You handed something off, explained what you needed, and assumed your team member understood. Then the work came back wrong, incomplete, or late. Maybe it didn’t come back at all until you went looking for it.
So you fixed it yourself. And somewhere along the way, you probably thought, This is why I don’t delegate. It’s easier if I just do it myself.
I understand the frustration. But before you decide delegation doesn’t work, I want you to consider another possibility: What if the problem wasn’t the person? What if the handoff wasn’t as clear as you thought it was?
Your team can’t read your mind
One of the most common delegation mistakes I see is an owner transferring confusion instead of clarity.
Sometimes that’s because the owner isn’t actually clear about what he wants. He knows there’s a problem. He knows something needs to get done. But he hasn’t slowed down long enough to define exactly what he’s asking someone else to accomplish.
Other times, he is clear in his own head. The problem is that he assumes everyone else can see what he sees.
You’ve been carrying this business for years. You know the customers, the history behind the project, what “good” looks like, and which decisions matter. You’ve accumulated context that your employee simply doesn’t have.
Then you say, “Can you take care of this?” and assume the rest is obvious.
It isn’t.
When the work comes back differently than you expected, it’s easy to conclude that the employee wasn’t ready for the responsibility. Sometimes that’s true. But sometimes you expected him to intuit information you never actually gave him.
A clear handoff answers six questions
Before you delegate an important project or task, there are at least six things the other person needs to understand.
1. What exactly are you asking them to do?
Not the vague category of work, but the actual assignment.
2. What supporting information or resources do they need?
They shouldn’t have to discover halfway through the project that there’s a document, customer conversation, budget constraint, or piece of history you forgot to mention.
3. Why does this matter?
Context helps people make better decisions. If they understand how the assignment connects to the mission, the customer, or a larger business objective, they’re better equipped to exercise judgment when something unexpected happens.
4. What does winning look like?
How will both of you know whether the job was done well? If you’ve got a standard in your head but never communicate it, you can’t reasonably expect someone else to hit it.
5. When is it due?
“Soon,” “when you get a chance,” and “I’d like to get this moving” aren’t deadlines.
6. What authority are you actually giving them?
Can they make decisions? Spend money? Talk directly to the customer? Change the plan? Or do they need your approval first?
If those things aren’t clear, you haven’t really delegated responsibility. You’ve handed someone an assignment surrounded by unanswered questions.
Want some help getting clear before your next handoff? The Delegation Handoff Kit will walk you through these six questions and help you create a clear, written handoff for your next project or task.
Delegation is an intentional transfer
There’s a principle here that goes deeper than management technique.
In 2 Timothy 2:2, Paul tells Timothy to take what he has heard from Paul and entrust it to faithful men who will be able to teach others also.
And what you have heard from me in the presence of many witnesses entrust to faithful men, who will be able to teach others also.
Notice the progression. Paul has taught Timothy. Timothy knows what he’s been entrusted with. Now he’s responsible for intentionally entrusting it to other faithful men who can carry it forward.
That’s very different from vaguely pointing at something and hoping the next person figures it out.
I’m not suggesting Paul was giving Timothy a six-step business delegation framework. He wasn’t. But I do think we see a principle worth paying attention to: if something matters enough to entrust to another person, we should care about whether we’ve transferred it faithfully and clearly.
And that’s especially important if you’re trying to build a heritage business.
Your business can’t grow beyond what you can entrust to others
Your business will never grow very far beyond your personal capacity if everything important still depends on what you can personally do, remember, decide, or fix.
At some point, you have to become capable of entrusting meaningful responsibility to other people. Otherwise, no matter how many people you hire, you’re still the ceiling on what the business can accomplish.
That requires more than finding better people. It requires becoming a better leader.
Learning to delegate clearly is one of the skills that allows the business to become something more than the sum of your personal capacity. It’s part of building something that can grow, endure, and eventually be entrusted to others.
Before you blame the person, audit the handoff
Take the most recent project or task you delegated that didn’t go well and reconstruct the handoff as honestly as you can.
What exactly did you tell them to do? What supporting information did you provide? Did you explain why it mattered? Did you define what a successful outcome looked like? Was there a specific deadline? Did they know what decisions they were authorized to make?
Here’s the important part: Don’t answer based on what you knew. Answer based on what you actually communicated.
You may discover that your employee really did drop the ball. Delegation doesn’t remove accountability.
But you may also discover something more uncomfortable and more useful: you expected clarity from them that you never provided yourself.
That’s something you can lead.
The goal isn’t to make delegation foolproof. It’s to get good enough at transferring clarity and responsibility that important work can move forward without requiring you to personally carry all of it.
If you want to build a business capable of growing beyond you, learning to make that transfer well isn’t optional.
To thriving,
- Zach
