Delegating Tasks with a Clear Handover: Result, Framework, Feedback

Why do delegated tasks so often land back with the owner?

Almost every owner knows the pattern. A task is handed over, usually in passing. After a few days the questions arrive, then an interim result that does not fit, and in the end the owner does it after all, because it is faster. Next time, he delegates less. The company grows, but decisions stay on one desk.

The essay from founder to business owner describes why letting go is a leadership task. This article goes one step further into practice and asks the guiding question: What must a handover look like so that a delegated task stays with the employee and the result is still right?

To answer it, we first clarify what delegating means exactly and introduce a thinking model, principal-agent theory, that explains the typical breaking points. Then we weigh two perspectives based on studies and move on to the handover in three questions, with an example and a conversation guide.

Whoever hands over an activity gets questions. Whoever hands over a result with latitude gets responsibility.

What does delegating mean, and what is it not?

Delegating means assigning a result to a person and leaving the decisions needed along the way to them. Overall responsibility toward customers and the company remains with the owner. Responsibility for the result is transferred.

Two related things need to be distinguished from it. Whoever only gives an instruction transfers an activity but no decision. That is sometimes right, for example with a new colleague in her first week. And whoever dumps a task transfers it without a goal or framework, usually because it is a nuisance. That looks like delegating but almost always ends in reverse delegation.

The levels are not a ranking of employees but a property of each task. The same person can work at level 4 on complaints and at level 2 on discounts. What matters is that both sides know which level applies. Most questions arise because the owner means level 3 and the employee has understood level 1.

The thinking model: delegating as a principal-agent relationship

Principal-agent theory describes relationships in which a client, the principal, has an appointed party, the agent, act on its behalf. It goes back to Jensen and Meckling (1976) and is usually applied to owners and managers. But it fits just as well to the owner who gives a task to an employee. How the theory plays out in day-to-day business as a whole is described in the essay when employees decide differently than the owner.

The theory identifies two breaking points. First, information asymmetry: the agent knows more about the status of the work than the principal, and the principal knows more about what he actually wants than he says. Second, diverging goals: the owner thinks about margin and customer relationships, the employee about a manageable workday and about not making mistakes. Both are legitimate, but not automatically the same.

The theory answers these breaking points with three means: clear agreements on the result, information about progress, and an allocation of decision rights that fits knowledge and risk. Translated into a small business, this means: the result must be spelled out, the framework must reflect the company’s goals, and feedback must be arranged before work begins. That is exactly what the handover described below does.

Does delegating really produce better results? Two perspectives

The first perspective says: delegating relieves the owner and motivates the team, so everything improves. The second, often unspoken: delegating costs quality and control, because nobody knows the customer as well as the owner. Both perspectives contain some truth, and research allows a more precise answer.

Kim, Beehr, and Prewett (2018) analyzed 55 independent samples in a meta-analysis that examined how employees respond to leadership that transfers responsibility and latitude. The strongest relationship was with employees’ evaluation of the leader (a correlation of 0.59); the weakest, but still positive, was with behavior and performance (0.31). There was no reliable relationship with employees’ emotions. For small companies there is a matching individual finding: in 196 interviews with owners of small service businesses in the United Kingdom, transferring responsibility to employees was associated with sales growth (Altinay, Altinay, and Gannon 2008). Both studies show associations, not proven effects.

The second perspective gets support from another direction. Zhu, Smith, and Brown (2024) conducted 44 in-depth interviews with 30 founders of Canadian technology companies and 14 managers those founders had hired. Many founders experienced handing over decisions as an attack on their sense that the company is “theirs.” The authors found three ways of dealing with this: some gave up the sense of ownership entirely, some held on to the old control, and some reinterpreted it. These founders no longer saw their role as deciding everything, but as shaping the company: direction, values, standards. Only on this third path did the handover succeed permanently. Where founders kept intervening in delegated decisions, the managers reacted with disappointment.

This leads to a reasoned assessment. Delegating improves performance, but not automatically and not as strongly as morale. Quality depends on the handover, and the handover depends on the owner. The study by Zhu and colleagues is qualitative and limited to young technology companies. Its finding nevertheless matches a rule that applies to every company: whoever promises latitude and then restricts it again loses more trust than if he had never granted it.

The results handover in three questions

The essay from founder to business owner introduced the results handover with five fixed points. For daily use, they can be grouped into three questions that match the title of this article.

• Result: What exists at the end, and how do you know it is good? This includes the deadline, with date and time.
• Framework: Which limits apply, for example regarding budget, margin, or quality? This includes latitude: what may be decided without asking, meaning which of the four levels applies?
• Feedback: When and how do you learn about the status without having to ask?

If one of the five points is missing, the task will come back sooner or later. Latitude is missing most often. The owner says what he wants but not what the employee may decide on her own. Then every small deviation becomes a reason to ask, and a level 3 handover effectively becomes level 1.

For tasks involving several people, handing over to one person is not enough. Then it must also be clear who co-decides and who is only informed. The tool for this is described in the article on how to clarify responsibilities with the RACI matrix.

How does a 15-minute handover conversation work?

1. State the reason and the purpose (2 minutes)

   Why does the task exist, and what is the result needed for? Whoever knows the purpose decides special cases correctly.

2. Agree on the result and deadline (3 minutes)

   One verifiable sentence and a date. “By Thursday at noon, every customer with an invoice more than 90 days overdue has received a call and an agreed payment date.”

3. Set framework and latitude (4 minutes)

   Name the limits and state the level explicitly. “You decide installment plans of up to three months yourself; anything beyond that, talk to me.”

4. Arrange feedback (2 minutes)

   When, in what form, how short. “Wednesday evening, a message with three numbers: called, payment date agreed, still open.”

5. Have it repeated (2 minutes)

   The employee summarizes result, latitude, and feedback in their own words.

6. Clarify resources (2 minutes)

   Which templates, lists, or access rights are needed, and where are they?

Whoever has held the conversation this way once notices that it takes hardly longer than the usual handover in the hallway. The difference shows in the days that follow. A worked example illustrates how much time this saves.

What to do if the task comes back anyway?

Even after a good handover, there comes a moment when the employee is at the door with a problem. Whether the task stays with them is decided in the next two minutes. Three questions from the essay on the owner’s change of role help: “What do you suggest?”, “What do you need to decide this yourself?”, and “What is the worst that could happen if you are wrong?”

If a result looks different from how you would have done it but stays within the agreed framework, it is good. Whoever corrects the path afterward takes responsibility back. You fix shortcomings through the framework of the next handover. A study of 74 teams from 17 South Korean companies also points to a trap that easily arises in small teams: whoever gives individual employees much more latitude than others worsens the exchange of information within the team and thus its performance (Hu et al. 2025). Latitude should therefore depend on the task and be understandable to everyone.

Conclusion: how a handover transfers responsibility

The guiding question was what a handover must look like so that the task stays with the employee and the result is still right. Principal-agent theory provides the explanation: handovers fail because of information gaps and unspoken goals. The answer is therefore a complete handover with three questions: which result by when, within which framework with what latitude, and which feedback when.

As shown, according to research, transferred responsibility mainly improves attitudes and motivation, and performance to a smaller but measurable extent. Where owners pull delegated decisions back to themselves, on the other hand, they lose their people’s trust. The result is sober: delegating is not an act of trust that either succeeds or fails, but a craft with five components that can be learned.

What you can do this week

1. Write down three tasks that regularly end up back with you.
2. For each, check which of the five points was missing in the last handover.
3. Set the latitude level for each task and state it explicitly to the person responsible.
4. Hold the next handover as a 15-minute conversation following the guide above.
5. Make feedback on delegated tasks a fixed item in your weekly planning.

If you want to hand over sales step by step, you will find the signals for it in the essay on handing over sales. The handover from this article is the tool for it on a small scale.