Delegation Is Not Handoff: A Working Guide for New Managers

Now you are convinced delegation does not work and that it is faster to do everything alone. It is, for about three weeks, until your calendar is a wall of things only you can do. Delegation fails for a boring reason: the person receiving the work does not know where their authority ends. They know the task. They do not know what they are allowed to decide.

Hand over outcomes, not activity

"Put together the quarterly numbers" is activity. "By the 10th, the leadership team can see where we stand on the four metrics and what changed since last quarter" is an outcome. An outcome tells the person what good looks like, so they can make a hundred small decisions without asking you. If you cannot describe the finished thing in one sentence, you are not ready to delegate it. You are ready to define it.

Name the three levels of authority

Write down, explicitly, which of these applies. Most friction disappears the moment you do.

• Decide and inform: they make the call, then tell you. Use when the stakes are low and the decision is reversible.
• Recommend and confirm: they bring a recommendation with reasoning; you approve or redirect. Use when the stakes are moderate.
• Gather and advise: they research and present options; you decide. Use when the stakes are high or the relationship is sensitive.

The levels are not a ranking of their ability. They are a property of this specific task. Be explicit that a "gather and advise" task is not an insult, and be explicit when a task moves up a level.

Transfer context, not just instructions

People cannot make good decisions in a vacuum. Give them the two or three things you know that they do not: why this matters, who will push back, what has already been tried, and what a bad outcome would cost. Twenty minutes of context buys back hours of rework.

Set the check-in before they need it

The worst check-in is the one that happens after something has gone wrong. Agree on the rhythm up front and make it small: a two-line message at the halfway point, a fifteen-minute review before the final version. Then honor it. If you skip the check-in, they assume the work is fine. If you add surprise check-ins, they learn that you do not trust them.

Resist the rewrite

When the first version comes back and it is seventy percent right, the temptation is to take it and fix it yourself. Do not. Send it back with specific notes: "The structure works. Section two needs the comparison against last year, and the recommendation needs one sentence of reasoning." Your goal is a person who can do this next time, not a document that is perfect today.

Every task you rewrite instead of coach is a task that comes back to you forever.

Say the quiet part

Tell them why you are handing this over. "I am giving you this because you need to be able to run it without me by spring." That sentence changes how the work is received. It turns delegation from a burden into a message about their future.