In my book, I share the story of a business owner who left his company to attend a conference. While he was away, his team received a last-minute change to a request for proposal. The revised response was due that same day, and several decisions had to be made before it could be submitted.
The team understood the work and knew the opportunity mattered. What they did not have was the authority to make those decisions without the owner.
They tried to reach him, but he was unavailable. Nobody believed they had the right to act, so the deadline passed and the company lost the contract.
It would be easy to blame the employees. Someone should have stepped forward. Someone should have shown initiative and made the call.
But the problem existed long before the RFP changed.
The owner had given his team responsibility for completing the work while retaining the authority to make the decisions that shaped it.
He had not delegated. He had reassigned work.
The Work Moved. The Decisions Did Not.
Many leaders believe they are delegating because someone else is completing the task.
They assign the report, hand over the project, remove themselves from the meeting, and place another person’s name beside the deliverable. On paper, the responsibility has moved.
Then the first meaningful decision appears.
Can we adjust the timeline? Can we commit additional resources? Can we change the approach? Can we accept this risk?
Suddenly, everything returns to the leader.
The leader may no longer be doing the work, but they remain the only person permitted to decide how it gets done. This may remove some activity from their calendar, but it does nothing to develop the team’s ability to operate independently.
The leader eventually becomes frustrated because nobody takes initiative. Yet the system has taught everyone that their role is to complete the predictable parts of the work and return to the leader whenever judgment is required.
The problem may not be a lack of initiative. It may be the logical result of how the leader has structured authority.
Why Leaders Hold On to Authority
Most leaders do not deliberately create this situation. They hold on to authority because doing so feels responsible.
They have more experience, recognize risks faster, and have usually dealt with similar situations before. When pressure increases, providing the answer often feels like the safest and fastest option.
Sometimes it is. The problem comes when the exception becomes routine.
If every difficult decision returns to you, your experience becomes a ceiling for everyone else. Your people may become highly capable at execution, but they will never develop the judgment required to lead without you.
There is another reason leaders struggle to let go: being needed can feel good.
When every important question comes through you, you remain at the centre of the operation. Your expertise is reinforced, you maintain visibility over the details, and people continue to depend on your direction. From inside that system, dependency can easily be mistaken for leadership.
But the number of decisions requiring your involvement is not proof of your value. In many cases, it shows how little decision-making capacity you have developed around you.
Accountability Without Authority Is a Setup
You cannot reasonably hold someone accountable for an outcome while reserving every meaningful decision for yourself.
If they cannot adjust resources, negotiate priorities, change the approach, or respond when conditions shift, they do not own the result. They are administering your plan.
That matters because plans rarely survive unchanged. Priorities move, timelines shorten, new information appears, and assumptions prove wrong. Someone can follow every original instruction and still fail because the situation no longer resembles the one for which those instructions were written.
Genuine delegation allows the person closest to the work to respond within established boundaries. They understand the desired end state, know what they are authorized to decide, and recognize when a decision exceeds their authority.
Without that clarity, even strong performers learn to protect themselves. They wait, seek permission, and make sure consequential decisions belong to someone above them.
What looks like passivity may simply be someone protecting themselves because they are responsible for the result but not trusted to make the decisions.
Delegation Requires Tolerance
Watching someone else exercise authority can be uncomfortable, especially when they choose an approach different from yours.
They may take longer to reach a decision. They may weigh risks differently, structure the work another way, or produce a result that is fully acceptable without looking anything like the result you would have produced.
That does not mean the delegation failed.
Too often, leaders compare another person’s developing judgment against their own years of experience. That is an unfair comparison that creates an impossible standard.
If the only acceptable decision is the one you would have made, you have not delegated authority. You have asked someone to reproduce your preferences.
Throughout my own leadership experience, I have focused on the desired end state. If the team’s plan will achieve that end state, stays within the established boundaries, and does not introduce unacceptable risk, then it is good to go. It does not need to be my plan.
I step in when the proposed approach will not achieve the required outcome or when the consequences extend beyond the authority I delegated. I do not step in simply because I would have chosen a different route.
Delegation requires some tolerance for short-term inefficiency while another person develops judgment. You may need to coach through decisions that seem obvious to you. You may need to accept good work that does not look like your work. You may even have to allow mistakes the organization can safely absorb.
If you reclaim control whenever someone hesitates or takes a different approach, you teach them that authority is temporary and ownership exists only until you disagree.
Five Questions Before You Hand Over the Work
Effective delegation begins with a clear outcome. The person needs to understand the end state they are responsible for achieving, not merely the activity they have been assigned.
They also need explicit decision-making authority. Telling someone to “take ownership” means very little if they do not know which decisions they can make or whether you will support those decisions when challenged.
That authority still needs boundaries. Budget limits, policies, safety requirements, legal obligations, commitments to other teams, and risks outside the person’s area of responsibility may all affect what they can decide independently. Clear boundaries allow people to act without guessing where their authority ends.
Both sides must also understand when the leader needs to become involved and how progress will be assessed. Delegation does not mean disappearing until the deadline. Oversight remains necessary, but it should support ownership rather than quietly take it back.
Before handing over a meaningful responsibility, answer five questions together:
- What outcome do you own?
- What decisions can you make without me?
- What boundaries must you operate within?
- When do I need to become involved?
- How will we assess progress and success?
If either person cannot answer those questions, the delegation conversation is not finished.
When the Question Comes Back to You
Even when authority has been clearly delegated, people will still return with questions. They may be facing an unfamiliar situation, checking their understanding of the boundaries, or developing confidence in their judgment.
Your response will shape what happens the next time.
If you immediately provide the answer, you solve the current problem but teach the person to find you whenever uncertainty appears.
A better starting point is:
“What do you recommend?”
Now they must assess the situation, consider their options, and form a judgment.
If the recommendation is sound and falls within their authority, confirm that the decision belongs to them. If their thinking needs work, question their assumptions, ask what other options they considered, or identify a risk they may have missed.
You are still providing leadership, but you are strengthening their thinking instead of taking the decision away.
Some situations will exceed the authority you delegated, and the decision will need to return to you. The objective is not to remove yourself from every consequential decision. It is to ensure decisions only return when your involvement is actually required.
Did You Actually Delegate?
The company in the opening story did not lose the contract because its employees lacked the ability to complete the work. It lost the contract because the authority to act was trapped inside one unavailable person.
The work had been distributed, but the organization still depended on the owner.
The next time someone returns with a decision you thought you had delegated, resist the urge to immediately question their initiative. First ask yourself whether you actually gave them the authority to make it.
What decisions keep returning to you because nobody is certain they have the right to make them?
Answer that honestly. You may discover that the next step is not asking your team to take more ownership. It is deciding what authority you are finally prepared to release.