The Hard Part of Delegating Is Not Letting Go

A task travels easily because it explains nothing

A manager hands off a report, a meeting agenda, a first draft, and it goes cleanly, because the task needs no explanation. The instruction is complete on its own: prepare this, deliver it by this date. The person receiving it already knows what to do, because the task repeats and its edges are fixed. The manager teaches nothing, because there is nothing to teach.

The same manager reaches a decision and finds no such ease — which vendor to keep, when a complaint escalates past the team, whether a hire clears the budget it was supposed to fit inside. These questions carry no instruction, because the manager never followed one in making them. The calls were made on a judgment built up over years, and that judgment was never written down anywhere — not because it was hidden, but because it was never asked for.

This is where delegation actually gets hard, and it is usually misdiagnosed. The manager reads the stall as a trust problem — the team isn't ready, or: I don't trust them with this yet. The real issue sits closer to home: the manager has no instruction list either. What exists is years of accumulated feel, and feel has never had to be said out loud.

The manager knows the call, never named the rule

Ask a manager how they pick which vendor to keep and the answer comes fast and confident: I look at price, lead time, track record. Ask the same manager how those three criteria were weighted against each other across the last ten decisions, and the answer slows down. Ranking the criteria is a different act from making the call, and the manager has made the call a hundred times without ever once ranking it.

Making the call and teaching the call are two different jobs Having made a decision correctly is not the same thing as knowing the rule behind it — one is experience, the other is that experience translated into language. A manager can pick the right vendor for a decade without ever stating, even to themselves, how the three criteria were weighted in any given case. Because the decision keeps landing right, nothing ever forces the rule into words.

The moment delegation is attempted, that gap surfaces without warning. Telling a team member to "weigh price, lead time, and track record" is not an instruction, because the three can conflict — the cheapest vendor may be the slowest, the fastest may have the weaker record. The manager resolves that conflict silently, in a weighting that has never been named, one exactly as old as the decision itself and exactly as invisible.

Without a rule, what transfers is a guess

When a manager hands off a decision without ever writing the rule, what the team member actually receives is not a rule but an inference drawn from the manager's past calls. That inference usually works, because a manager's decisions carry a pattern and an attentive team member learns to read it over time. But the gap between an inference and a rule shows up exactly where the pattern runs out — in the case nobody has seen before.

• On a decision that fits the pattern, the team member acts with confidence, because similar cases have already been seen.
• On a decision that falls outside it, they hesitate, because what they are holding is a guess, not a rule, and they do not know where the guess stops applying.
• The hesitation sends the decision back up, the manager reads it as "not ready yet," when what it actually proves is that no rule was ever written.

A piece on the habit of taking a decision back after handing it off covered a later version of this same failure — the manager delegated the task but kept pulling the decision back. This is an earlier point in the same chain: the manager genuinely wants to let go, but there is no rule in hand to let go of, only an intuition that was never put into words. The two problems look similar and need different fixes.

Writing the rule is a different skill than making the call

Making a decision well and writing down the rule behind it look like the same skill and are not. The first grows through repetition — the more vendors a manager picks, the sharper the instinct gets. The second does not grow on its own, because writing the rule requires something repetition never asks for: looking back over past cases and asking, in each one, which factor actually decided it, and why.

A manager can be highly experienced and still have no rule written down, because accumulating judgment and naming it afterward are two separate acts of attention. This explains why delegation is often hardest for the most experienced managers — the sharper the instinct, the less that manager has ever had reason to examine what the instinct is made of, since it has always simply worked.

The skill of writing the rule can be learned, but only by looking at one's own past decisions as a stranger would — laying out the last ten vendor choices and sorting out, case by case, which factor actually carried the decision. That work is slower and more uncomfortable than making the call again, because it is usually the first time the manager sees how uneven their own judgment has been.

From the room

In the coaching room, this gap tends to surface through one question: "You want to hand this decision off — what would your team need to know to make it the way you do?" Most managers cannot answer cleanly on the first try, and the hesitation is rarely a sign of incompetence. It usually means the rule has simply never been asked for before.

The answer tends to arrive in pieces — one criterion, then an exception, then an exception to the exception. The process is tiring, because the manager has to narrate a decision back to themselves that they have only ever made, never explained. Until that narration exists, nothing has actually been delegated, because what was handed off was never an instruction — it was a guess.

What the first conversation usually does is put into words a decision the manager has been running silently for years. Requesting a conversation starts with saying that quiet rule out loud for the first time.