The Principles of Effective Delegation
The Principles of Effective Delegation
Most managers do not fail at delegation because they refuse to do it. They fail because they delegate the way they were once delegated to: a quick word in the corridor, a vague deadline, and a surprise two weeks later when the work comes back different from what they had in mind. Then they conclude that it is faster to do it themselves, and the pile on their desk grows again.
The principles of effective delegation are not complicated. There are five of them, and every serious model — from management textbooks to the "five rights" that nurses are taught — is a variation on the same short list. What separates managers who delegate well from those who do not is simply that they apply all five every time, including the two that feel like extra work.
Principle 1: Define the result, not the activity
"Can you look into the supplier problem?" is not a delegated task. It is an invitation to guess. An effective handover names the outcome, the deadline and what "done" looks like: "By Thursday noon, a one-page comparison of our three freight options with total landed cost per container, and your recommendation."
The test is simple. If the person could finish the work and you could still say "that's not what I meant", the task was not defined. Write the definition of done in one or two sentences, and have the other person repeat it back in their own words. Most misunderstandings surface in those thirty seconds rather than in the review meeting a week later.
Principle 2: Match the task to the person — and say why
Delegation is not the same as offloading. The right person is someone with the skill to do the job, or with most of the skill and a reason to learn the rest. Hersey and Blanchard's situational leadership model is still the clearest way to think about this: a person new to a task needs direction and close contact, while an experienced person who knows the work needs little more than the goal and the deadline.
Tell people why they were chosen. "I'd like you to take this because you handled the Izmir tender well" turns an extra task into a signal of trust. "Nobody else was free" turns the same task into a chore, and the quality of the work usually follows the message.
Principle 3: Give authority that matches the responsibility
Nothing kills delegated work faster than responsibility without authority. If the person must deliver the freight comparison, they need permission to call the forwarders directly, access to last year's invoices, and a clear budget limit for any decision they may take on your behalf.
It helps to state the level of freedom out loud. Jurgen Appelo's Management 3.0 describes seven levels of delegation, from "I will tell you" through "we agree together" to "you decide and I don't need to know". You do not need all seven in daily practice, but you do need to say which one applies. "Decide, and tell me afterwards" and "recommend, and I decide" are very different jobs, and people should not have to guess which one they were given.
Principle 4: Agree the check-ins before the work starts
Control is not the opposite of trust; unannounced control is. Agree at the handover when you will look at progress — for example a ten-minute call on Tuesday and the final version on Thursday — and then leave the work alone in between. The person knows when you will look, and you are protected from discovering on Thursday that the work went in the wrong direction on Monday.
Keep the check-ins short and about the result: what is done, what is blocked, what needs a decision from you. If you find yourself redoing parts of the work during a check-in, go back to principle one — the definition of done was probably not clear.
Principle 5: Accountability stays with you — and so does the credit you pass on
You can delegate the task and the authority. You cannot delegate the accountability. If the freight comparison is wrong, your director will still ask you about it, and that is how it should be. Accepting this makes delegation calmer: you stop looking for someone to blame and start looking at how the handover could have been better.
The reverse also holds. When the work is good, say so, in front of the people whose opinion matters to the person who did it. Recognition is what makes the next delegated task a welcome one.
Watch where the monkey lands
In 1974 William Oncken and Donald Wass published "Management Time: Who's Got the Monkey?" in the Harvard Business Review, and the journal has reprinted it many times since. Their point was that the "next move" on a problem — the monkey — tends to jump back from the employee's back to the manager's. "Let me think about it and get back to you" is the classic jump.
The five principles are, in practice, a way of keeping the monkey where it belongs. A defined result, the right person, real authority and agreed check-ins leave the next move with the person doing the work. When someone walks in with a problem, the useful question is not "what should we do?" but "what do you recommend, and what do you need from me to do it?"
What the "C's of delegation" add
Many training courses teach delegation as a list of C's — three or four of them, depending on the trainer. The words differ, but they usually include clarity (what exactly is expected), capability (whether the person can do it), communication or check-in (how progress will be followed) and control (what stays with the manager). Read side by side with the five principles above, they cover the same ground under different labels. Pick one version and use it consistently in your team, so that everyone means the same thing by a "proper handover".
The most common delegation mistakes
- Delegating only what you dislike. People notice quickly when they only ever receive the unpleasant work, and motivation falls with it.
- Taking the task back at the first difficulty. It teaches the person that problems travel upwards and that the manager will eventually do it anyway.
- Delegating to the same two reliable people. They burn out, and the rest of the team never gets the chance to grow.
- Measuring the method instead of the result. If the result meets the definition of done, the path someone took to get there is theirs to choose.
The same principles work at home
Participants in our leadership courses often tell us, somewhat to their own surprise, that the hardest delegation they face is not at the office. It is at home, where two working adults share a household and one of them ends up holding most of the invisible planning: remembering the dentist, noticing that the detergent is running out, deciding when the car needs its service.
The mechanics of the problem are the same as in any team. "Can you help more with the kids' stuff?" is the household version of "can you look into the supplier problem" — an activity, not a result. Couples who split the work well tend to do exactly what good managers do: they hand over a whole area rather than single errands, agree what "done" means (the school forms are signed and returned, not just seen), give the other person the authority to decide how it gets done, and agree when they will look at it together instead of checking up on each other every evening.
Some couples keep this on a shared list or a whiteboard in the kitchen. Others use an app built for it: Alpacto, for example, lets two people agree on a task, its deadline and what counts as finished, and then records that it was done — the kind of written handover that works at the office and saves a lot of arguments at home. Whichever tool you choose, the principle is the one this article started with: a task that is not defined has not been delegated.
A one-minute delegation checklist
Before you hand over the next piece of work, check that you can answer five questions:
- What is the result, by when, and what does "done" look like?
- Why this person, and what support do they need?
- What may they decide without asking you?
- When will you look at progress, and how?
- How will you recognise the result when it is delivered?
If one answer is missing, take two more minutes before the handover. It is still faster than doing the work yourself — and much faster than doing it twice.
Delegation, feedback and follow-up are practised with real cases from participants' own teams in our Effective Leadership and People Management training in Istanbul. For the structured thinking behind good decisions, see also our article on problem solving and decision making techniques and the note on why leadership skills matter for managers.
Frequently asked questions
What are the 5 principles of effective delegation?
Define the result and the definition of done; match the task to the right person; give authority that matches the responsibility; agree check-ins before the work starts; and keep the accountability with the manager while passing the credit on.
What are the levels of delegation?
Models differ. Jurgen Appelo's Management 3.0 uses seven levels, from the manager deciding alone to the team deciding without informing the manager. In daily practice it is enough to state clearly whether the person should recommend, decide and report, or decide alone.
Can accountability be delegated?
No. A manager can hand over the task and the authority to carry it out, but remains accountable for the result towards their own manager.
Why do managers find it hard to delegate?
The most common reasons are the belief that doing it yourself is faster, fear of losing control, and bad experiences with past handovers — which are usually the result of an unclear definition of done rather than of the people involved.
(By: Peter Frans – Principal Consultant & Trainer)