How to Delegate: Five Levels of Leadership Delegation

“I delegated it, but it still came back to me.” Many leaders know this pattern. The task was assigned, yet questions, approvals and decisions continued to flow upward until the leader was effectively doing the cognitive work again.

The problem is that delegation is often treated as the transfer of a task. Strong delegation transfers a defined outcome and an appropriate amount of decision space.

Five levels of delegation

A practical way to make delegation explicit is to distinguish levels rather than using the word as if it always meant the same thing.

1. Investigate and report. Gather the relevant information; I will decide.
2. Recommend. Analyze the options and bring me a recommendation; I will make the final choice.
3. Decide with approval. Make the proposed decision, then obtain approval before acting.
4. Decide and inform. Make the decision within the agreed boundaries and tell me afterwards.
5. Own the outcome. Carry the result and make the necessary decisions independently within the defined mandate.

None of these levels is inherently better. The correct level depends on capability, risk, reversibility and the organizational mandate available.

Start with the outcome

Delegation becomes weak when the leader explains the activity in detail but leaves the expected result vague. Define what needs to be true when the work is complete. What quality criteria matter? Which constraints are fixed? Which parts of the method are open?

Clear outcomes reduce the temptation to manage every intermediate step.

Transfer decision rights explicitly

A person cannot own an outcome while needing approval for every meaningful choice. State which decisions are theirs, which require consultation and which must still be escalated. This is especially important when several functions are involved and informal approval habits have grown over time.

Define boundaries without prescribing the process

Useful boundaries can include budget, legal constraints, customer impact, deadlines or non-negotiable quality standards. Boundaries protect the system. They should not become an excuse for telling the person exactly how to do the work.

Set a review rhythm that matches the risk

New or high-risk responsibility may need an earlier review. Established work may require only an agreed outcome check. The review point should be clear before the work starts so that support does not become constant monitoring.

Three traps that pull work back upward

The quality trap: “I could do it better.” Perhaps — but the role question is whether the result is sufficiently strong and whether capability is growing.

The speed trap: “It is faster if I do it myself.” Usually true once; expensive when repeated.

The identity trap: “If I am no longer the person solving everything, what is my contribution?” Leadership requires a different answer to that question.

When delegation fails, inspect the system

If work repeatedly returns, ask why. Is the expected outcome unclear? Does the person lack competence or information? Are decision rights missing? Is the leader reopening choices after delegating them? Is another stakeholder bypassing the delegated owner?

Each diagnosis leads to a different intervention. Simply telling the team to “take more ownership” rarely fixes a structural ownership problem.

A delegation sentence worth making explicit

“You own this outcome. You may decide these things yourself. These are the boundaries. Come back to me if this threshold is crossed. We will review the result on this date.”

When those elements are clear, delegation becomes less about letting go emotionally and more about designing responsibility well.