Delegating tasks without them coming back to you as questions
Delegating tasks means handing a task to someone else together with the authority it takes and the responsibility for the result. If you only hand over the work but keep the decisions, you've handed out an assignment. The task then comes back to you as a question. Many owners of a business with a team know this from experience: they hand something off, and a week later half of it is back on their desk. In this article, we explain what delegating involves, why it so often fails in small businesses, which five questions should be answered before every handoff and how to delegate to your team and to AI employees.
Task, authority, responsibility: the three belong together
Management literature often says that task, authority and responsibility have to match. That sounds theoretical, but day to day it's very concrete:
- The task is what needs to get done: writing quotes for standard inquiries, checking incoming invoices, coordinating appointments.
- The authority is what the person may decide on their own while doing it: which price to set, whether to approve an invoice, whether to move an appointment.
- The responsibility is answering for the result: if something goes wrong, it's clear who sorts it out.
Without the authority, every decision comes back to you as a question. Without the responsibility, nobody feels in charge when something gets stuck. Without a clear task, everyone does something different. Delegating only works when all three are handed over together.
What delegating isn't
Three things often get called delegating, but they aren't:
Assisting. "Do it exactly like this, and ask me before it goes out." That can make sense, for example at the start of onboarding. But the responsibility stays with you, and so does your time.
Dumping. An unpleasant task gets handed off, but without authority and without support. The person can only fail or ask.
Letting go without feedback. The task has been handed off, and nobody reports back. You don't know what's done, so you check for yourself, and then you're steering again.
Why delegating so often fails in small businesses
The usual advice is: delegate. In small businesses, the task still often comes back, because the workflow isn't written down, special cases have no rules, there's no report or nobody has time. When the business depends on its owner covers these four reasons in detail. What they have in common: what's missing is the handoff, not your team's goodwill.
What you can delegate, and what stays with you
Not every task can be handed off equally well. We distinguish between thinking and doing. Where your own judgment is needed, say on a strategy, a difficult customer conversation or a new offer, the work stays in conversation with you. What simply has to get done can be handed off, to a person or to an AI employee.
On top of that comes a house rule: for decisions about people, about money and with legal consequences, a person stays involved in our approach. That doesn't mean these tasks can't be delegated. It means there's a sign-off point at these spots where a person decides, and that the limit is written down beforehand.
Some things stay with the owner too: the direction of the business, choosing the people and deciding what gets handed off next. Delegating those means handing over the leadership.
Five questions before every handoff
Before you hand off a task, five questions should be answered, ideally in writing:
- What's the result? How can you tell the task is finished, and what has been produced by then?
- What may the person decide, and what not? Where are the hard limits at which they stop and ask?
- Which variants are there? Which special cases come up regularly, and what's different about them?
- Where does an unclear case go? Who gets a case that doesn't fit the rules, and how does it turn into a new rule?
- What report do you get? What do you hear about, when, and in what form?
These five questions aren't random. They're also in our process profile, our word for a process description: end, the work for each variant, report, escalation path and hard limits. Once the task becomes a recurring process, trigger and start come on top, and you have a process profile. The template is in How to document business processes: the template for handing a process to an AI employee. For shorter tasks, a checklist is often enough, as described in How to create a checklist your team actually uses: structure, template and the step to an AI employee.
Delegating in levels
A task is rarely handed off completely overnight. For processes that AI employees take over, we distinguish four autonomy levels. As an analogy, they also help when you learn how to delegate to people:
- Autonomy Level 1, Assisted: The AI employee does its task when someone starts it, and your team checks every run. With a person: they do it, and you look at it every time.
- Autonomy Level 2, Autopilot: It starts on its own on a schedule or trigger, runs through to the final report and hands anything uncertain to a person. With a person: they do it independently, report back and only come to you with the unclear case.
- Autonomy Level 3, Audited: An AI manager reviews its work and bundles the reports, so you only see the exceptions. With a person: a team lead bundles things, and you see the exceptions.
- Autonomy Level 4, Autonomous: The process has passed the week-away test and keeps running even when you're away for a week. With a person: the task keeps running even when you can't be reached for a week.
The advantage of looking at it this way: you don't have to decide whether to hand off a task "completely". You only decide which level it's at right now and what's missing for it to move up one level. The details are in The four autonomy levels: how a process in your business runs on its own.
Leading after you delegate
Leadership only starts with the handoff. Two habits decide whether a task stays handed off.
Answer questions with a rule. When a question comes in, the quick answer is tempting. But it only solves this one case. Better to ask back, "What would you suggest?", followed by a rule that applies next time. That way, every question grows what the person can decide on their own.
Look at the exceptions regularly. Not at every task, but at whatever didn't fit the rules. Where exceptions pile up, a rule or an authority is missing. For us, this happens in the feedback conversation after a case comes through the escalation path, and once a month when we look at all processes.
And there's one habit to drop: taking the task back the first time it wasn't done the way you would have done it. That's the quickest way to get your team to stop making decisions on its own.
Delegating to AI employees
You delegate to an AI employee by the same rules. And one of the three parts stays with a person: responsibility for the result. It sits with you or with the contact person on your team named in its job description. In our approach, it first gets a job description: role, task, rights and limits are set in writing, plus a contact person on your team. That settles what it may do and what it may not. Then comes the trial task: watching, training, each variant once with someone next to it. It's only signed off after several clean runs and a period in which your team monitors side by side.
The difference from a person lies in one place: an AI employee doesn't weigh things up where the rules end. If it's unsure, it doesn't guess; it hands the case to a person on your team. That's why it's a good fit for tasks that simply have to get done, and your team keeps the ones that need judgment. What the first phase looks like is covered in Autonomy Level 1, Assisted: when your team checks every run.
What this looks like for us
At a tax advisory firm, filing tax assessment notices sat with the office team. It was delegated to an AI employee: the task (filing the notices) and the authority to assign them itself according to around 45 rules, plus a completion email after every run. Responsibility for the result stays with people at the firm: anything the AI employee can't match with certainty goes to the office team, and the AI employee is trained on it afterwards. So the office team handed off the task but kept the escalation path. Both processes are at Autonomy Level 2, Autopilot, as of September 2026.
In Kevin's own business, 14 AI employees work, each with a personnel file, a fixed role and clear limits. The hardest part, reviewing their work, Kevin hasn't fully handed off yet: an AI manager reviews their work, and that role is still on trial. With delegating, too, Kevin tries new levels in his own business first.
Runs without me
Every two weeks, one process that runs without the owner: what came in, what the AI did, where a person decided. Two minutes to read.
Worksheet
Process Potential Check
With five questions and a first process list to fill in, you find the process that could run on its own first. Comes as a PDF by email once you confirm your sign-up.
Strategy session
In a 20-minute strategy session, you tell us where things get stuck. We'll tell you honestly whether an AI employee is a good fit for you.
Book a strategy sessionFrequently asked questions
What does delegating mean, in simple terms?
You hand off a task together with the right to make decisions while doing it and the responsibility for the result. If you only hand off the work and keep the decisions, the task comes back to you as a question.
What is reverse delegation?
That's when a task you've handed off travels back to the owner as a question or a problem. Usually a rule or an authority is missing. The answer is a new rule, not taking the task back.
Which tasks shouldn't I delegate?
The direction of the business, choosing the people and tasks where your own judgment is needed. For decisions about people, money and with legal consequences, a person stays involved at a sign-off point in our approach.
How do I delegate when nobody on the team has time?
Then it's worth looking at the routine work that eats up time today. What simply has to get done can be taken over by an AI employee, and your team gets time for what you want to hand off.
Read more
How to set what a role decides on its own, what follows a procedure and what only a person decides is described by Kevin in What Can an AI Lead Role Decide? How new people take over tasks is covered in Employee onboarding checklist: bringing new people up to speed when you've been explaining everything yourself, and how to keep the overview in KPI dashboard for a business with a team: a few metrics you actually read.
Your next step
Which task have you handed off three times, only for it to come back three times? On the call, we look at whether Owner Autonomy is a fit for your business and which process is worth starting with. That's also where we go over how it works and what it costs.