Team & ownership
How to delegate tasks without every decision coming back to you
You have handed over the task, but every question and approval still comes back to you. A useful handover includes more than instructions: the team needs to understand the expected outcome and which decisions it can make independently.
1. Delegate an outcome, not just an activity
“Look after the customers” leaves too much open. “All new enquiries are recorded and have a next action by the end of the working day” describes an outcome you can review. The person taking ownership also needs access to the information and systems required to deliver it.
Before handing over, check capacity, experience and access. Even a clearly defined task can fail if it is simply added to a full working week. Discuss which existing responsibility should become a lower priority.
2. Define what can be decided without you
Ownership needs decision boundaries. Otherwise the team does the work while you remain the approval point for everything. Explain the normal case, limits and exceptions.
- Decide independently: for example, arrange appointments within available time slots.
- Follow an agreed rule: for example, prepare standard quotes using approved prices.
- Ask for approval: for example, offer special discounts, make unconfirmed delivery commitments or change contract terms.
Adjust the boundaries to the task and the person's experience. A new colleague may need closer coordination initially. Reduce that coordination deliberately as their experience grows. Reviewing every minor decision indefinitely prevents the team from becoming more independent.
3. A handover template you can use
- Outcome: Every enquiry is recorded, answered or has a documented next step.
- Owner: Name the responsible person and their backup.
- Information: Link to the contact list, approved prices and response template.
- Decision boundaries: Give standard information independently; obtain approval for individual commitments.
- Deadline: An internal response target appropriate to capacity.
- Escalation: Who decides when something is unclear, and how urgent cases are raised.
- Review: A regular time to discuss open items and recurring questions.
Ask the colleague to explain their approach in their own words. This reveals different expectations early. Handling the first case together can be more useful than writing additional pages of documentation.
4. Separate everyday questions from escalations
Questions are part of learning. The aim is not to eliminate them altogether. But avoid immediately solving every issue that falls within the agreed decision boundaries. Ask for a proposed answer and identify what information is missing.
Urgent cases need a separate route. These might include an upset customer, a deadline at risk or a decision outside the colleague's authority. Agree which channel to use and who covers when you are unavailable. Customer or financial commitments should not be improvised because someone is unsure.
5. Review the handover rather than every action
Start with a short, scheduled review. Look at open tasks, exceptions and questions that keep recurring. A repeated question may indicate a missing rule, access permission or training need.
Review your own behaviour too. If you take over without discussion or repeatedly reverse decisions, the team will start waiting for approval again. Change the boundaries explicitly rather than silently introducing new expectations.
A useful sign of progress is fewer routine decisions coming back to you while important exceptions still reach you on time. Assess both together. Fewer questions are not an improvement if colleagues have simply stopped reporting problems.
Which task should you delegate first?
Choose a recurring activity with limited risk and a clear outcome. Routine follow-ups or preparing standard quotes may be more suitable than complex contract negotiations. Keep the scope small enough to review together after a week.
If an unclear workflow prevents the handover, start with our small business process template. If responsibilities are unclear across the team, a business process audit can help prioritise the underlying issues.
