To delegate without micromanaging, define three things before the work begins: the expected outcome, the decisions the person can make independently and the points when you will review progress. Explain required constraints, but do not prescribe every step unless the method itself matters.
Why doing the work yourself feels faster
Doing a task yourself may be faster today. You already know the context, where the information sits and whom to contact when something is missing. Explaining that to someone else can take longer than completing the task.
The problem appears when the same work returns next week or next month. If the knowledge remains with you, decisions continue to wait for you. Employees keep asking for approval, and routine work competes with responsibilities that only you can handle.
This does not mean every task should be delegated. It means recurring work deserves a proper handover rather than a rushed list of instructions.
Delegation includes decision authority
Assigning a task tells someone what to do. Delegating responsibility gives them ownership of an agreed result and enough authority to achieve it.
Suppose you ask an employee to prepare a weekly report. If they still need your approval to choose the data, contact colleagues, correct obvious errors and decide how to present the information, you have passed on the administration but kept every decision.
A practical handover covers three areas:
Outcome: What must be true when the work is complete?
Boundaries: Which decisions can be made independently, and which still require approval?
Checkpoints: When will progress be reviewed, and what should be ready?
These three points provide direction without turning every action into an approval request.
Define the outcome before explaining the process
Start with the result, not the sequence of steps you would follow personally.
A clear outcome answers four questions:
What must be delivered or completed?
Who will use the result?
What information must it contain?
What makes it acceptable?
“Prepare the weekly report” names the task, but not its purpose. A clearer brief would be:
“Prepare a report for Monday’s management meeting. It should show current sales, overdue orders, expected cash receipts and any issues that require a management decision.”
This gives the employee room to choose a suitable method while making the expected result specific.
Before explaining your own process, ask: “What approach would you take, and where do you expect to need input?” The answer shows whether the person understands the objective. It can also reveal missing information before the work starts.
Set clear decision boundaries
Decision boundaries should cover three types of information:
Independent decisions: Choices the person can make without asking you.
Constraints: Budgets, deadlines, policies, customer commitments and other limits.
Approval points: Decisions that still require your involvement.
A useful test is whether a decision is easy to reverse. Reversible choices can often remain with the person doing the work. Examples include changing a report layout, reorganising internal tasks or requesting routine information from a colleague.
Decisions with serious financial, legal, contractual or customer consequences may still require approval. For example, an employee might prepare a response to a customer complaint but need approval before offering compensation above an agreed amount.
Avoid instructions such as, “Use your judgement, but check with me if anything important comes up.” The word “important” leaves the boundary open to interpretation. Name the specific limit instead, such as a spending threshold, a change to a delivery commitment or a decision affecting a signed contract.
Use checkpoints without taking back control
A checkpoint is a planned review of progress. It is not an opportunity to approve every small action.
Agree in advance on:
When the review will happen.
What should be ready by then.
Which open questions should be discussed.
What would justify an earlier conversation.
The number of checkpoints should reflect the person’s experience, the uncertainty of the task and the cost of correcting a mistake late. Familiar, low-risk work may need one short update. New or consequential work may need an early review and additional agreed points.
Review unfinished work early enough to change direction. Waiting until the deadline may leave you choosing between accepting the wrong result and taking the task back. Checking constantly creates the opposite problem. The employee learns to wait for your approval rather than make decisions.
A useful checkpoint might be:
“Prepare the proposed structure and one completed section by Wednesday afternoon. We will check whether the report answers management’s questions before you complete the rest.”
This catches misunderstandings without requiring approval for each figure or formatting choice.
A practical handover example
A step-by-step handover for a weekly management report might sound like this:
“Open the sales spreadsheet, copy the figures into this template, update these cells, email these three people for missing numbers and send me the completed version for approval.”
The employee can follow the instructions, but the purpose and decision authority remain unclear. If the source data changes or someone does not reply, the task is likely to return to you.
An outcome-based handover is more useful:
“Prepare a report for Monday’s management meeting. It should help us identify sales changes, overdue orders, expected receipts and issues that need a decision.
You can choose the layout, contact department leads for missing information and correct obvious data-entry errors. Ask for approval before changing a reported financial figure if the correct value cannot be confirmed.
Prepare the proposed structure and one sample section by Wednesday. We will review whether it gives management enough information before you complete the first full version.”
This brief defines the result, the available authority and the first review point. It does not require the employee to copy the owner’s process exactly.
When not to delegate yet
Delegation is not always the right immediate choice. Ask four questions:
Is the intended outcome clear?
Can the decision boundaries be defined?
Is there enough time for the person to learn?
Is the work likely to recur?
If several answers are no, clarify the task, postpone the handover or retain it temporarily.
Do not delegate an unclear objective. Assigning it to someone else does not remove the ambiguity. Define the intended result first.
A genuine one-off crisis may also require immediate action rather than a full handover. However, repeated emergencies should not automatically remain with the owner. If the same problem keeps returning, it may need a clearer process and owner.
Final approval may also need to stay with you when the person lacks the authority, information, experience or resources to accept the consequences of a decision. State exactly what they own and where your responsibility begins.
Frequently asked questions
How much detail should I provide when delegating?
Provide enough detail to define the outcome, constraints and decision authority. Explain the procedure when a specific method is required for legal, safety, contractual or operational reasons. Otherwise, let the person propose an approach.
What if the person chooses a different method from mine?
Compare their method with the agreed outcome and boundaries. A different approach is not a problem if it produces an acceptable result and respects the constraints. Intervene when it creates a material risk or cannot achieve the outcome, not simply because you would do it differently.
How often should I check progress?
Base checkpoints on experience, uncertainty and the cost of late correction. New or high-risk work may need an early review. Familiar and reversible work may need only a short update or final check at an agreed time.
Which decisions should still require approval?
Retain approval for decisions whose consequences the person is not authorised or equipped to accept. These may include significant spending, contractual changes, legal commitments or serious customer consequences. Define the limits in advance so routine decisions do not keep returning to you.