Delegation is often understood as passing work on so that a manager has more time. That is only half right. When a manager transfers tasks without clarifying decision rights, completion criteria, and escalation thresholds, work may leave the manager’s desk while decisions still return to the same place. The organization does not truly become faster; it simply gains more requests for approval and more meetings to resolve matters that the team could have handled itself.
Good delegation does not remove the manager from the work. It designs a space in which the person receiving the work can act responsibly, knows when to coordinate, and knows when to pause and seek a decision. When that space is clear, employees can exercise judgment, while the manager gains time for choices that genuinely require a broader perspective.
Distinguish assigning work from assigning decision rights
A functional leader can ask an employee to prepare a proposal, contact a supplier, or track progress. That is task assignment. Yet if every change to a discount, deadline, cost, or message must wait for the leader’s approval, decision rights remain concentrated at one point. As workload rises, that point becomes a bottleneck: the manager is overloaded, response is slow, and employees learn to wait for instructions rather than prepare options.
Giving decision rights does not mean allowing everyone to act as they wish. Before the work begins, it should answer three questions: what may the assignee decide; which boundaries may not be crossed; and which information must be brought upward so that the manager or relevant group can decide together. These questions matter more than a vague instruction such as “please handle this proactively.”
| What to clarify | Useful wording | Risk when left open |
|---|---|---|
| Result to achieve | “Settle an option so the customer receives a response before 16:00 today.” | The assignee focuses on activity without knowing which outcome takes priority. |
| Decision right | “You may adjust delivery dates by up to two days within the approved budget.” | Small decisions repeatedly return to management. |
| Escalation threshold | “If a customer commitment must change or cost exceeds 10%, raise it before confirming.” | Bad news arrives late, or the team reports everything out of fear. |
| Review point | “Give a short Wednesday update: choice, risk, and support needed.” | The manager learns of the problem only after the deadline has passed. |
Set boundaries by risk, not by a habit of control
Many managers retain even minor decisions because a mistake happened in the past. The reaction is understandable, but if every matter needs permission, the organization never learns how to handle risk. A more practical approach is to classify decisions by reversibility and impact if wrong. Decisions that can be corrected quickly, have little customer impact, or involve low cost should usually be delegated close to where the work occurs. Decisions that alter an important commitment or affect reputation, legal exposure, safety, or a large budget should rise to the appropriate level.
Boundaries should also be written in work language rather than slogans. “Be careful” tells an employee little about what to do. “You may refund up to VND 500,000 in a case with clear evidence; any public complaint or exception must go straight to the team lead” is actionable and reviewable. Over time, boundaries should be reconsidered using real cases, not preserved simply because they were once issued.
Example: a customer at risk of leaving
A B2B software company receives a complaint from an important customer about an implementation error. If the customer-success employee is assigned only to “monitor the case,” they may have to wait for several approval levels for every step. Instead, the functional leader can define a clear scope: the owner may coordinate the technical team, arrange a customer update that day, propose a service extension up to a set limit, and seek support from other functions. They must escalate immediately, however, if the issue concerns data security, risks contract termination, or requires a commitment beyond existing terms. This arrangement enables a rapid response while retaining major risks at the right decision level.
Do not turn reporting into a permission ritual
Delegation often fails at the update stage. Some organizations require reports so detailed that employees spend time proving they worked; others have no review rhythm, so managers recognize a problem only when options are limited. A useful update focuses on decisions and exceptions: what has been decided, what direction results are taking, what new risk has appeared, and what support the assignee needs.
A short update can use four lines: objective, choice made, evidence available, and decision or resource required. When the manager responds, the emphasis should be on the quality of reasoning and use of evidence, rather than taking over every detail. This is how employees learn judgment while managers see early where intervention is needed.
Turn errors into data for adjusting authority
An error does not automatically prove that delegation is impossible. After an incident, the relevant questions are: was the decision scope too broad or too vague; was needed information available; was the escalation threshold understandable; and did the assignee have sufficient capability and support? An error within the assigned scope may show that guidance or training needs adjustment. An error that crosses a stated boundary may require a review of accountability. The two situations should not be treated in the same way.
Managers also remain responsible for the delegation system. They cannot hand work over and assess only the final result without considering whether the assignee received context, authority, and resources. By redesigning scope, recording exceptions, and carrying lessons into the next assignment, delegation becomes a capability-building mechanism rather than a temporary way to reduce workload.
Conclusion
Delegation matters when it lets decisions be made close to the best available information while retaining control over major risks. Start with one recurring job, specify the result, authority, escalation threshold, and update rhythm. After several cycles, adjust the boundaries using real situations. The team will then receive not only more work, but a genuine ability to take responsibility and act.
References
Yukl, G. (2013). Leadership in organizations (8th ed.). Pearson.
Hackman, J. R., & Oldham, G. R. (1980). Work redesign. Addison-Wesley.
Simons, R. (1995). Levers of control: How managers use innovative control systems to drive strategic renewal. Harvard Business School Press.
