How to Delegate Results, Not Methods

Delegation is where most first-time managers fail, and the reason is sympathetic rather than lazy. You were promoted because you were good at the work. You can see the route. Watching someone take a different and slower one is physically uncomfortable, so you hand over the task and keep the method.

That is not delegation. It is supervision with an extra step, and it costs more than doing the work yourself.

The distinction

Delegating a method sounds like: do this, then this, then send it to me before it goes out. The person executes your thinking. Nothing has moved off your desk except the typing, and you remain the only one who understands why it is done that way.

Delegating a result sounds like: this is what needs to exist by Thursday, this is what good looks like, here is what you cannot spend or break, come to me if you hit one of those limits. How they get there is theirs.

The second version is slower the first three times and then permanently faster, because you now have someone who can do the thing without you in the room.

What has to be specified

• The outcome. What exists at the end.
• The standard. Specific enough that they can judge it themselves.
• The deadline.
• The constraints. Budget, people, anything that cannot be touched, decisions that are not theirs to make.
• The checkpoint. One agreed moment to look at it together before it is finished.

The checkpoint is what makes this survivable. Without it you either interrupt constantly or find out on the deadline that it went wrong in week one. Agree it in advance and then leave the space between alone.

It will be done differently, and worse at first

That is the price, and there is no version of the job where you avoid paying it. If you intervene every time the route differs from yours, you have taught the person that the objective is to guess what you would have done, which is a skill of no value to anyone.

The test for whether to step in is not whether it is how you would do it. It is whether it will meet the standard by the deadline within the constraints. If the answer is yes, leave it alone even if it offends you.

What not to delegate

• Anything involving someone’s performance, pay or employment.
• Bad news to the team. It comes from you.
• Whatever you would only hand over because it is unpleasant. That one is visible from a long way off.

Everything else is a candidate, including things you enjoy. Especially things you enjoy, in fact, because those are the ones you are keeping for reasons that have nothing to do with the team.

You keep the responsibility

Delegating the work does not delegate the accountability. If it goes wrong, it went wrong on your watch, and the answer upward is that you own it, without a name attached.

This is what makes delegation feel risky, and it is also what makes it real. A manager who delegates and then distances themselves from the outcome has not built any trust, they have just relocated the blame, and the team works it out immediately.

The signal you are sending either way

A manager who still takes the hard tasks has told the team that difficult work belongs to the manager. The predictable result is that people stop attempting difficult work, and then you conclude that the team cannot handle it.

You are measured by what the team produces, not by what you produce. Every hour you spend doing work that somebody else should own is an hour of your actual job that is not getting done.

Related: leading a team for the first time and managing people who were your peers.