Delegation Is Not Dumping: The Accountability Loop

There is a kind of hand-off every employee recognizes instantly: the task that arrives with no context, no authority, and a deadline already sweating — dumped, not delegated. And there is a kind every manager recognizes from the other side: the task you handed over and then quietly redid at midnight because checking on it felt harder than doing it. Both failures get blamed on delegation, and neither is delegation. Delegation is a loop, not a toss: a brief that holds, boundaries that are clear, check-ins that are agreed, and a reckoning at the end that runs in both directions.

The brief is where delegation succeeds or fails

A brief that holds answers five questions before the work starts. What outcome is needed — not what steps to take, but what “done” looks like. Why it matters, because people solve problems better when they know which problem. What authority travels with the task: what the owner may decide alone, what needs a consultation, what stays with you. What the real deadline is and what drives it. And what resources and access come with it. Most failed delegations were never briefed at all — they were mentioned. A mention transfers a task. A brief transfers the means to succeed at it, and the difference shows up three weeks later, at the worst possible moment, in work that answers a question nobody asked.

Check-ins are the loop, not the leash

The middle of the loop is where managers sabotage themselves, in one of the two directions above. The disappearing manager confuses trust with absence and learns about problems at the deadline. The hovering manager confuses diligence with control, reviews every step, and teaches the owner that the assignment was theatre — the real decisions still live upstairs. The discipline between them is agreed checkpoints: short, scheduled, set at the start, at which the owner reports progress, surfaces problems early, and gets decisions only the manager can make. Problems raised at a checkpoint are cheap. The same problem raised at the deadline is a crisis, and it usually belongs as much to the loop as to the work.

Choose what to hand over — and refuse what comes back

The loop starts before the brief, with the choice of what to delegate at all. The right assignments sit in a specific band: work the owner can plausibly do, stretched by roughly one level beyond what they have already proven — close enough to reach, far enough to grow. Hand over only what you could do blindfolded and you have assigned a chore and called it development. Hand over the crisis of the quarter and you have set a person up to be the story of a failure. And the loop has a defensive skill as well: refusing reverse delegation, the moment a stuck owner tries to hand the problem back — “what do you think I should do?” answered with a decision made upstairs. The loop-preserving answer returns the thinking with support: what have you considered, what would you recommend, what do you need from me to proceed? The task stays where it was delegated, and so does the growth.

The loop closes with accounting — the step almost everyone skips. The finished work is reviewed against the brief, not against the manager’s unspoken preferences. Credit goes to the owner, publicly, by name. And the accounting runs the other way too: where the brief was unclear, the priorities changed mid-stream, or a checkpoint was missed, the manager owns that part out loud. That symmetry is what makes the next delegation work. People accept real accountability from managers who visibly accept their own.

← All Insights