Delegation Is Not Dumping: Handoffs That Stay Done

Every manager has said the same sentence: "I could do this faster myself." It is usually true, and it is always the wrong reason. Doing it yourself once is faster. Doing it yourself forever is how you become the bottleneck of your own team, and how the people under you never grow. Delegation is the skill that separates managers from super-employees, and it is almost always done badly.

The problem is that most delegation is actually dumping: the task is thrown over the wall with no context, no standard, and no follow-up, and it comes back wrong, late, or not at all. The fix is not to delegate more. It is to delegate properly, which is a system, not a decision.

1. Delegation Is a Transfer of Ownership, Not a Task Assignment

The moment the task is handed over, it is no longer yours. It belongs to the person who received it, and that includes the right to do it differently, make mistakes, and solve the problem their own way. Managers who delegate but keep their hands on the steering wheel do not have a delegation problem, they have a trust problem, and the team can feel it.

The test is simple: after the handoff, can the person change the approach without asking permission? If the answer is no, you have not delegated, you have outsourced the typing. Real delegation transfers the outcome and accepts a different path to it.

2. Delegate Outcomes, Not Steps

A well-delegated task is described by its outcome: the result that counts as done, the quality bar it must meet, and the deadline. A badly delegated task is described by its steps: "email X, then call Y, then format the report." Step-based delegation creates workers who follow instructions and stop when the instructions run out.

The outcome description forces the other person to think. It also gives them room to find a better way, which is the entire point. "Get the report to the board by Thursday, with the revenue section matching the finance numbers" is a delegation. "Write these five paragraphs" is a task, and it will be back on your desk the moment the list is exhausted.

3. Match the Task to the Stretch

Delegation is not only for tasks the person can already do. The growth version is the stretch: a task just beyond their current level, with support and a safety net. This is how people actually develop, not through training courses but through real work with real consequences, at a size they can absorb.

The judgement is the level of stretch. Too small and the person is bored and you are still doing the work. Too large and they drown and you spend the week rescuing them, which is worse than doing it yourself. The right size is the task that makes them uncomfortable but not panicked, with a check-in scheduled before the deadline, not after the disaster.

4. Context Is the Secret Ingredient

The number one reason delegated work comes back wrong is not lack of skill. It is lack of context. The person does not know why the task matters, who is waiting for it, what happened last time, or where the bodies are buried. They cannot make the judgement calls that the task requires, because they do not have the map.

Before you hand anything over, spend the extra ten minutes on context: the history, the stakeholders, the reasons behind the deadline, the mistakes to avoid. The person will still make mistakes, but they will be new mistakes, in new territory, not the same mistakes you already mapped. That is the difference between delegation and archaeology.

5. Define Done Before You Define the Work

Most delegation arguments come from a mismatch on the definition of done. The manager imagines a polished deliverable, the team member delivers a rough draft, and both sides feel cheated. The fix is to agree on done at the start: what it looks like, what it includes, what quality level, and what "good enough" means for this particular task.

Write it down if it matters. A one-sentence definition of done, agreed before the work starts, eliminates more friction than any amount of follow-up after the fact. "Done means the numbers reconcile to the finance system and the summary is under one page" is a contract. Without it, everyone is guessing.

6. Follow Up on the System, Not on the Person

Managers make the follow-up wrong in both directions: they either hover, checking in daily and signalling distrust, or they disappear and wait for the deadline to reveal the disaster. The right pattern is a scheduled check-in at a natural midpoint, focused on the system, not the person.

"Where are the blockers?" is a system question. "Are you done yet?" is a pressure question. The midpoint check-in exists to remove obstacles: a missing approval, a broken tool, a decision that needs to be made. When the follow-up is about removing barriers, it is welcome. When it is about surveillance, it is resented, and the work gets slower, not faster.

7. Debrief and Institutionalise

When the delegated work comes back, the loop is not finished. The debrief is where the learning happens: what went well, what was harder than expected, what would be done differently next time. Ask the person before you tell them, and let their assessment come first.

The final step is institutionalising the win. The task that went well should not need to be delegated again next month, it should be owned, permanently, with the standard written down. Delegation that repeats the same task to the same person forever is a failure of growth. Delegation that converts a task into an owned responsibility is the whole game.

8. The Manager Who Has Nothing to Do

The measure of a manager is not how much they do. It is how much gets done without them. A team where every task needs the manager's input is not a team, it is an appendix. A team where ownership is distributed, standards are written, and outcomes are defined is a machine that runs.

Delegation done well feels strange at first, because it creates empty space in your calendar. That space is not idleness. It is the room for the only work you should be doing: the problems too big to hand over, the strategy nobody else can see, and the next level of the people you are supposed to be growing.

Tags

#management #leadership #productivity