Delegate the decision, not just the task

Delegation works when a person receives a clear outcome, enough authority and information to act, and a practical boundary for review and escalation.

The owner asks a colleague to handle a task, then receives a stream of questions about every small choice. That may be poor judgement, but it may also be an unclear delegation. Responsibility was handed over while the authority to make decisions remained with the owner.

Delegation becomes useful when the person understands the outcome, the boundaries and the decisions they can make independently. It also requires a review rhythm that gives the owner visibility without turning every step into a request for permission.

Define the outcome before the activity

Arrange the delivery is an activity. Ensure the agreed order reaches the customer by the confirmed date, with proof of receipt and any exception raised promptly is a clearer outcome. It tells the person what good completion looks like.

Ask what information is necessary. A colleague cannot exercise sound judgement if the customer promise, budget or quality standard is missing. Supplying those inputs is part of the delegation, not an optional favour after the work begins.

Avoid writing a procedure so detailed that it removes every useful decision. Some work needs strict steps, particularly where safety or compliance matters. Other work needs a clear outcome and room to choose an appropriate method. Match the control to the consequence.

State the authority boundary

Name the decisions the person can make, the limits that apply and the matters that require approval. A purchasing responsibility might include an agreed budget, approved suppliers and a threshold for exceptions. A customer service responsibility might include specific remedies and escalation triggers.

Do not assume that a job title makes those boundaries obvious. Different owners expect different levels of independence. A colleague who has previously been criticised for making a decision may seek approval even where the owner now says to use initiative.

A useful conversation includes examples near the boundary. Ask what the person would do if a supplier changes a price, a customer rejects delivery or an urgent request conflicts with the agreed plan. Those examples reveal ambiguity before it becomes an operational problem.

Separate visibility from permission

The owner may need to know what is happening without approving every action. Agree what will be reported, how often and which exceptions require immediate contact. Routine updates and escalation are different channels serving different purposes.

A short decision log can preserve visibility. Record the choice made, the reason and any issue that needs review. This is especially useful while a person develops confidence or takes on a new area of responsibility. The log should support learning, not become a second task larger than the work itself.

Independence grows when the boundary is clear enough for somebody else to act inside it.

Review judgement with evidence

When a decision goes wrong, examine the information available at the time, the agreed boundary and the reasoning used. A poor outcome does not automatically mean the decision was unreasonable. Equally, a lucky outcome does not prove that a weak process was sound.

Identify whether the problem was missing skill, missing information, an unclear rule or failure to follow an agreed responsibility. The corrective action should match the cause. Training cannot repair a contradictory approval system, and a new checklist cannot replace necessary judgement.

Keep consequences fair and proportionate. Delegation does not remove accountability. It makes accountability more specific by clarifying what the person was responsible for and what support the organisation provided.

Start with a recurring, bounded decision

Choose a decision that occurs often enough to practise and is reversible enough to review safely. Define the outcome, authority, constraints, escalation and review date. Let the person make the decision within that agreement. Resist quietly taking it back whenever a different but acceptable approach appears.

After several cycles, inspect whether questions have reduced, decisions arrive sooner and quality remains acceptable. Adjust the boundary when evidence supports it. Greater authority should follow demonstrated capability and reliable information, not simply the owner's exhaustion.

If every decision still returns to the owner, map the requests for a week. Look for repeated questions that could be answered by a clearer rule, better information or delegated authority. The pattern often shows where the next management improvement belongs.

What should a delegation agreement contain?

Keep the agreement short enough to use during the work. State the result, the person responsible, the decisions they can make and the conditions that require help. Include the information, budget and access available. A useful agreement can fit on a page if the task is bounded. Its value comes from shared understanding, not from the length of the document or the formality of the heading.

Ask the recipient to work through a recent example before the arrangement begins. Let them explain what they would decide, what they would record and when they would contact the manager. This reveals gaps that a simple question such as do you understand may miss. The exercise should also allow the person to identify a resource or authority they still lack. A handover is a conversation about workable responsibility, not merely the delivery of instructions.

How does the manager avoid taking the task back?

When a routine question arrives, refer to the agreed boundary before supplying the answer automatically. Ask what the person proposes and what evidence supports that proposal. If the choice falls within their authority, let them make it and record the result. The manager can remain available without becoming the decision maker for every step. Consistent behaviour matters because an informal habit can override a carefully written delegation agreement.

Do not change the boundary silently after an acceptable decision differs from your personal preference. Explain when a requirement was genuinely missed and when the choice was simply another reasonable way to reach the outcome. If the rule needs to change, state the change for future decisions. Retrospective criticism based on an unstated preference teaches people that the safest action is to return every choice to the manager.

When should authority expand?

Expand authority after observing reliable work within the current boundary. Look at the quality of decisions, the use of information, the handling of exceptions and the honesty of reporting. A person who raises uncertainty early may be demonstrating sound judgement rather than weakness. Likewise, someone who reports only success may still need closer review if problems emerge later through other channels. Confidence should follow evidence of how the responsibility is being exercised.

Choose the next boundary deliberately. It might involve a larger budget, a more varied type of exception or a longer interval between routine reviews. Preserve the controls that remain necessary. The aim is to move the appropriate decisions closer to the work while keeping accountability clear. If performance becomes less reliable, inspect the reason before withdrawing all authority. A change in workload, information or task complexity may explain the problem. Agree what needs to be restored, then test the arrangement again under conditions that the person can reasonably fulfil.

Write down one recurring decision today. Name who can make it, the boundary within which they can act and the exact condition that requires escalation. Then allow that agreement to do its work.