Delegating Tasks Without Taking Them Back

“It would be faster if I just did it myself.”

There are days when that is a perfectly reasonable thought. You know the task, the deadline is close, and explaining it would take time you do not feel you have.

But it is worth asking a second question: do you need to do this work yourself, or have you simply become used to being the person who does it?

Delegating is not a test of how much you can remove from your own calendar. Nor should it mean giving someone a vague assignment and hoping they figure it out. A more useful aim is to put a clear piece of work in someone else’s hands, with enough direction and support for them to take responsibility for it.

The difficult part is finding the balance. Stay too involved and the employee is carrying out your instructions while you still make every decision. Step away too far and they may be left guessing about expectations you never explained.

What are you ready to let someone else own?

Before choosing an employee, be clear about the work you want to delegate. Is it a defined task with an understandable result, or a collection of loose ends you have not yet sorted out?

Ask yourself what you would need to explain for someone to begin. If you cannot describe what a satisfactory result looks like, spend a little time clarifying that first.

Then consider the person’s experience, available time and interest in the work. Someone who already knows the task may need little direction. Someone learning it may need an example, access to a colleague or a chance to talk through an early attempt.

That preparation belongs in the plan. Do not call an assignment a development opportunity while leaving no time to learn it. Equally, do not give the same reliable person every additional task without discussing what is already on their plate.

A useful conversation is: “I’d like you to take responsibility for this. How does it fit with your current work, and what would you need from me?”

Be willing to change the timing, provide help or narrow the assignment. Keep work that requires your own authority with you; delegation is not a way around existing responsibilities or approval rules.

Which decisions belong to the employee—and which still belong to you?

This is where a broad request needs a little precision. “Please take care of it” does not explain whether someone can make a decision, recommend an answer or only gather information.

Take a routine example: asking a colleague to recommend a replacement for an aging office printer. The following is an illustrative assignment, not a company policy:

“Please recommend two options by Thursday. We need something that handles our usual document volume and works with our current computers. Include the purchase price and ongoing supply costs. You can choose which models to compare and ask our IT contact about compatibility. Bring me your recommendation before contacting a vendor or placing an order.”

Now the employee has a result to work toward and a clear limit on what they can decide. The manager has not prescribed every search or every line of the comparison.

Add any real budget limit or purchasing requirement at the outset. Make sure the employee can reach the information and people needed. A responsibility is not ready to delegate if essential access is still missing.

Once those boundaries are agreed, allow reasonable differences in how the work gets done. If the employee organizes the comparison differently from you, ask whether it answers the business question before changing it.

Your preferred method and a necessary standard are not always the same thing.

When does helping turn into taking over?

A question from an employee does not necessarily mean the assignment needs to come back to you.

If they ask which option to recommend, you might respond, “Which one do you think best meets our needs, and what concerns you about it?” Listen to their reasoning before supplying your own answer.

That is useful only if they have enough information to form a view. When a requirement was unclear or an important detail was missing, explain it. Making someone guess is not the same as encouraging them to think.

Agree on a check-in that fits the assignment. For the printer comparison, a brief conversation after the employee has identified possible options may be more useful than repeated requests for updates. It leaves room to correct a misunderstanding before the work is finished.

Also make clear when they should contact you sooner—for example, if no option meets an essential requirement or the agreed deadline is no longer realistic.

If you need to intervene, explain the reason and separate the part you must decide from the work they can continue. Avoid quietly redoing the entire task simply because that feels easier.

When the work is complete, review it against the expectations you agreed on. Be specific about what was useful and what needs improvement. Ask whether your original instructions and support were sufficient, too.

The point of delegation is not to disappear. It is to change your contribution: less time directing each move, more attention to the result, the boundaries and the support that makes the assignment workable.

Let the employee do the work. Keep your part of the agreement.

Further reading: Harvard Business School Online’s delegation guide discusses clear outcomes, appropriate authority and resources, and communication during delegated work.

Planning your next hire? Explore Summit Careers’ employer services.