Delegation

Most definitions say delegation is assigning tasks to someone else. True, and nearly useless, because handing out tasks is the part every manager already does. What makes it delegation is what travels with the work: the right to decide, the context to decide well, and ownership of the result. Take those out and you have a manager who kept the job and gave away the effort.

Why the simple definition misleads

It makes delegation sound like a scheduling problem you solve with a better task list. It is a control problem. Once you delegate properly, another person can do the work differently from how you would, and can get it wrong in ways you never would. That is not a side effect. That is the thing itself. Managers who say they are bad at delegating are rarely bad at handing out tasks. They are unwilling to accept a slightly worse version of a decision they used to make themselves.

The word also gets confused with three neighbours. Allocation distributes tasks while the judgement calls stay with you. Abdication hands over an outcome without authority, context or support, then reappears when it fails. Empowerment describes a climate rather than an act, and is often used to dodge the specific conversation. Delegation is a transaction between two named people about one outcome, and it either happened or it did not.

If the person doing the work still has to ask you before deciding anything that matters, you have not delegated. You have added a step.

What it looks like in practice

Delegation is observable, and you can spot it without asking anyone how empowered they feel. Where it is real, people can say what they are allowed to decide without checking. Work comes back finished rather than in fragments for approval. Someone makes a call the manager would have made differently, and it stands, because it sat inside the agreed limits. And when the manager is away, work does not queue up behind them.

A worked example. A team lead hands a client review to a newer manager. The weak version: send the template, ask to see the deck on Thursday, rewrite half of it that night, then answer the hard questions himself in the meeting. She has learned that her real job was producing a first draft. The delegated version: name the outcome (the client leaves knowing what changed, what it cost, what happens next), name the two constraints (no new scope, do not promise March), agree that she decides the structure and runs the room, set one checkpoint on Tuesday, then say almost nothing. The first version is faster once. The second is the only one that stops being needed.

Delegation vs allocation vs abdication

Read the columns as a diagnostic rather than a taxonomy. Almost nobody thinks they are abdicating, but the middle two are specific enough to check yourself against.

How to delegate properly

Delegation is a trainable management skill, not a temperament. The practices that move it are specific and slightly uncomfortable.

• Delegate the outcome, name the constraints. Say what done looks like, what cannot move (budget, date, legal, client relationship), and which decisions are theirs. Most briefs invert this: heavy on method, vague on the result. Hand over whole things where you can, because ownership of a fragment is not ownership.
• Match how much you hand over to how much they have already done. Andy Grove made this point in High Output Management: how closely you supervise should track experience with that specific task, not seniority in general. The same person can need close direction on something new and none at all on something they have run twenty times. Situational leadership says this in other language.
• Set the decision rights out loud. Decide and act; decide, act and tell me after; recommend and I decide; bring me options. Naming the level takes ten seconds and removes the ambiguity people otherwise resolve by asking permission.
• Hand over context, not just instructions. Why it matters, who cares, what has already been tried, where the sensitivities are. Most well-intentioned bad decisions happen because nobody said what the person was standing in.
• Agree checkpoints in advance, then stay out between them. A scheduled review is support. An unscheduled one is surveillance, and everyone can tell the difference. One-to-ones are usually the right place for them.
• Let the first attempt be worse than yours. If the standard is that they produce what you would have produced, you have set a test, not a delegation. Decide the bar that genuinely matters and accept anything above it.
• When they get stuck, ask before you answer. Handing over the answer trains them to come back. Asking what they would do if you were unreachable trains them to decide. The GROW model is a workable structure for this.
• Credit in public, correct in private. The SBI model keeps the correction about the work rather than the person.

None of this survives a team where being wrong is expensive. If people expect to pay for the judgement calls you handed them, they will hand every one back, and you will conclude, wrongly, that they were not ready. Psychological safety is what makes delegated authority get used rather than politely declined.

How to tell whether you are actually delegating

There is no clean metric here, and any dashboard claiming one is measuring something else. Watch for signals instead.

1. What happens when you take two weeks off? If decisions wait for your return, they were never delegated. Absence is the most honest audit there is.
2. In what form do decisions reach you? Requests for approval mean allocation. Notifications of what someone has already decided mean delegation.
3. Look at your own calendar. A manager whose week is full of work only they can do has usually given away tasks and kept the authority.
4. Count the reversals. Overturning a delegated decision occasionally is fine. Doing it often teaches people to stop deciding, whatever you say about ownership.

Be honest about what measurement cannot reach. Engagement surveys pick up how pleasant a manager is to work for, which is not the same as how much control they release, and time-tracking counts hours rather than authority. The reliable read is behavioural and shows up under pressure. Watch a manager when delegated work starts wobbling near a deadline. Most quietly take it back, then treat the result as proof the person was not ready. This is why simulation and experiential learning expose delegation habits faster than any questionnaire: put a group under a clock with more work than one person can hold, and within the hour you can see who kept the decisions.

Myths and common mistakes

• "It is faster to do it myself." For this instance, usually true. That is the trap. The arithmetic only works if the task never recurs, and the tasks that eat managers always recur.
• "Delegation means giving away accountability." It does not. You stay accountable upwards for the outcome. What moves is responsibility for the work and the authority inside it. Forget the first half and you abdicate. Forget the second and you micromanage.
• "They are not ready." Sometimes accurate. More often self-sealing, because readiness comes from doing things with real stakes, and they have only been given things without any.
• "Delegation is for the boring work." The work most worth handing over is often what you are best at and enjoy most, because that is the capability your team cannot build while you keep it.
• "Everything should be delegated." Some things should not be: performance and pay conversations, decisions needing authority the person does not hold, and anything where failure would land on them for a call that was really yours.

The through-line is simple. Delegation is not offloading work, and it is not a productivity technique. It is the deliberate transfer of decisions to someone who will make some of them differently from you, and the discipline to let that stand. Everything else is task management wearing a better name.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.