Many managers say they have delegated, yet employees still ask about every small matter. Elsewhere, work is delegated very broadly and problems emerge only after costs rise, customers complain, or a deadline has passed. These situations have the same cause: delegation stopped at “handle it proactively” and never made clear what the recipient may decide or which limits they must protect.
Delegation does not mean that a manager withdraws from the work. It means moving selected decision rights closer to the information and action while retaining decisions with major effects on money, customers, legal obligations, or direction. Clear boundaries from the outset help employees avoid waiting and help managers prevent issues that could otherwise have been stopped earlier.
Start with the result to be achieved
Do not start with an activity list. State the result the recipient must create, the deadline, and the minimum criteria for success. Instead of saying, “you are in charge of the customer event,” say: “you are responsible for an event for 80 guests, within a VND 180 million budget, with attendance of at least 70% of confirmed guests and no serious complaints.” Once the result is clear, the recipient can choose the method without asking about every step.
The criteria do not need to be numerous. Three to five are usually enough: objective, deadline, minimum quality, permitted cost or resources, and the main beneficiary. They also keep the later conversation focused on results rather than on how busy someone has been.
Specify three decision zones
A practical approach is to divide decision rights into three zones. In the first, the recipient may decide and only needs to update on the agreed rhythm. In the second, the recipient may prepare an option but must discuss it before finalizing. In the third, the matter must be escalated because it exceeds a risk threshold or commitment.
For example, a customer-service team lead may adjust shifts and offer a small goodwill benefit within the permitted budget. If a larger benefit is needed to retain an important customer, the lead prepares options and supporting figures, then requests approval. If the customer asks to change contract terms or seeks compensation, the matter must be escalated immediately. This is far more useful than the general instruction to “be flexible.”
Set thresholds before an incident occurs
Good boundaries are usually expressed as easy-to-recognize thresholds. A threshold may be an amount of money, a discount level, days of schedule delay, the scale of customer impact, a data type, or an irreversible commitment. When the threshold is clear, the recipient does not have to guess what a manager wants, and the manager does not need to monitor every detail.
For instance, a procurement manager may select from approved suppliers for orders below VND 100 million. A larger order, a new supplier, or non-standard payment terms requires review first. This rule does not slow routine transactions; it concentrates attention on decisions with greater consequences.
Agree when to report back
Delegation often fails because reporting comes too late or far too often. Agree when an update is sufficient, when early notice is required, and which channel to use. A weekly report may be enough for stable work. But a risk of delay, budget overrun, customer impact, or a changed assumption should be raised immediately rather than held until the end of the week.
A short template can work across many types of work: current status; change from plan; impact; options under consideration; and a decision needed, if any. This is not a device for micromanagement. It creates a shared view so the manager can support the work at the right time without taking back delegated rights.
Review after one cycle
Decision rights should not be treated as fixed from the first delegation. After one or two work cycles, a manager and employee should review three questions: which decisions still wait unnecessarily; which boundary is too broad or too narrow; and which information needs to appear sooner? If someone consistently handles a class of work well, their independent authority can expand. If one risk repeatedly occurs, the process or its review point should change.
Good delegation produces two outcomes at once: the person doing the work becomes more proactive, and the manager gains time for decisions only they should make. To achieve this, the instruction needs a result, decision zones, risk thresholds, and a reporting rhythm. Once these four points are clear, management no longer has to choose between letting go and holding every task.
