Read a sample: 1. Delegation Is a Decision, Not a Dump
The report is due Friday. On Tuesday afternoon, a manager forwards a chain of emails to a team member with a short message: “Can you take care of this?”
The employee opens the thread and finds requests from three departments, a spreadsheet with missing information, and a comment suggesting that the report may need a new format. She is not sure which version to use, whether she can contact the other departments directly, or who will approve the finished report. The manager is in meetings for the rest of the day.
Work has changed hands, but the manager has not yet delegated it well.
Delegation is a decision about more than who will perform a task. It is a decision about the result someone will own, the authority they will have, the support they can expect, and how the leader will remain accountable. A useful handoff does not require a long document or a formal ceremony. It does require enough shared understanding for the person doing the work to make progress without guessing at the essentials.
That distinction matters because most leaders do not intend to dump work. They are busy, they trust their people, and they want to move things forward. Yet urgency can turn “I’ll ask someone to handle it” into an incomplete transfer. The assignee inherits the uncertainty along with the work, while the leader assumes the assignment is underway.
Good delegation makes the transfer visible. It gives the other person room to contribute judgment while preserving a clear path for decisions, questions, and follow-through.
When you delegate, you assign responsibility for a defined piece of work and give someone an appropriate degree of authority to carry it out. Depending on the assignment, that person may plan the approach, coordinate with others, make certain decisions, and bring you a completed result. They may also bring you a recommendation if the final decision remains yours.
What you do not transfer is your accountability as the leader who made the assignment. If the work requires resources, you must help secure them. If your instructions conflict with another priority, you must help resolve the conflict. If a decision falls outside the assignee’s authority, you must make it or bring in the person who can. When the result affects others, you remain responsible for making sure the right people are informed and the outcome is reviewed.
This does not mean standing beside the employee for every step. Accountability is not the same as constant involvement. In fact, excessive involvement can make an assignment harder to own: the assignee waits for approval on choices they should be able to make, while the leader becomes a bottleneck.
Think of delegation as an agreement with two sides. The assignee is responsible for carrying the work forward, communicating progress, and raising issues within the agreed boundaries. The leader is responsible for making the assignment workable and staying engaged at the level the situation requires.
The balance will vary. An experienced colleague handling familiar work may need a brief handoff and a final review. Someone taking on an unfamiliar assignment may need earlier checkpoints, access to examples, and a clear route for questions. Neither arrangement is inherently better. The test is whether the arrangement fits the work and the person.
Task dumping is often recognizable by what is missing. A leader passes along work without enough context, time, authority, or support for the recipient to handle it effectively.
“Please own the client event” might sound empowering. But if the employee does not know the event’s purpose, budget boundaries, expected attendance, or who can approve commitments, the word own adds pressure without providing direction. The leader may feel relief at having handed it off; the employee is left to discover the assignment by trial and error.
Abdication goes a step further. It occurs when the leader treats the transfer as the end of their responsibility. An assignee encounters a problem that requires a leadership decision, but the leader remains unavailable or responds, “I gave it to you, so you figure it out.” The person may have been given responsibility without the authority to solve the problem.
Abdication can also appear at the end of an assignment. A leader who has not reviewed a result blames the assignee when stakeholders object, even though the leader never clarified the standard or made time to assess the work. Holding someone accountable is reasonable; making them solely responsible for a poorly designed handoff is not.
Simple instruction is different from both dumping and delegation. Sometimes the work calls for a specific action: “Please send the approved agenda to the project group this afternoon.” The result and method are clear, and little independent judgment is needed. That is a legitimate way to coordinate work. Not every request needs to become a development opportunity or a broad transfer of ownership.
The distinction is useful because it helps you choose deliberately. If you need a known action completed in a known way, give a clear instruction. If you want someone to manage an outcome, decide what judgment they can exercise and provide the conditions to use it. Problems arise when a leader expects the initiative of delegation but provides only a fragment of an instruction.
A leader’s retained responsibilities begin before the handoff. First, decide whether the assignment is appropriate to delegate. Some work may be restricted by organizational policy, confidentiality requirements, or the…