How to Delegate Without Micromanaging
Micromanagement is rarely a personality trait. It's what happens when a manager delegates a task without delegating a decision.
The situation
You handed off the vendor migration. Two days later you asked for an update. The day after that you asked to see the draft plan. By the end of the week you had rewritten half of it, and now you're doing the work you delegated while the person who owns it waits for you to finish so they can find out what they're supposed to be doing.
You know how this reads from their side. You've been on the other end of it. But the alternative — handing something over and finding out three weeks later that it went sideways — costs more than the awkwardness of hovering. So you hover, and the person gradually stops making decisions, which confirms your belief that they need close supervision.
Why it happens
Delegation fails at the handoff, not during the work. Most handoffs transfer the task and keep the judgment: do this thing, and check with me about anything that matters. The person receiving it now has responsibility without authority, which means every meaningful question has to route back through you. You then experience that routing as neediness, and they experience your impatience as a trap.
The second cause is unstated standards. You have a picture of what finished looks like — quality bar, format, who gets consulted, what's out of bounds. If you don't describe it, they'll build a different picture, and your corrections will feel arbitrary rather than informative. Arbitrary correction is the fastest way to train someone to stop moving without permission.
The third is fear of the visible failure. Delegation is a bet that a competent adult will do it about 80 percent as well as you would, and that the 20 percent is the price of having a team that grows. Managers who can't tolerate the 20 percent end up with a team that can't do anything without them, which is a much more expensive kind of failure and much harder to see.
The protocol
- 01Name the outcome, not the method. 'All fifty accounts migrated with no data loss by the 30th, and the sales team trained' — not a list of steps you'd take.
- 02Set the decision level explicitly, out loud, at handoff. Level one: do it and don't tell me. Level two: do it and tell me after. Level three: bring me a recommendation and I'll approve. Level four: bring me options and we'll decide together. Most conflict about micromanagement is two people operating at different levels without knowing it.
- 03State the constraints and the tripwires. Budget ceiling, non-negotiables, and the specific conditions under which you want to hear from them immediately — slipped date, cost over X, anything touching a customer contract.
- 04Agree the check-in rhythm at the start, and make it about the plan and the risks, not a task audit. Two scheduled checks beat six unscheduled ones.
- 05At the first check, review their plan before any work is done. This is where you buy most of your comfort back — the plan is cheap to correct, the finished work isn't.
- 06When it comes back at 80 percent, accept 80 percent. Give one piece of feedback for next time. Rewriting it yourself ends delegation permanently.
What to say
Handing something over properly
"You own the vendor migration. Fifty accounts, no data loss, done by the 30th, sales trained. You decide the sequence and the tooling without checking with me. Come to me before you sign anything over ten thousand or if the date is going to move. Send me your plan Friday, then we'll talk again the week of the 20th."
Catching yourself mid-hover
"I've been asking for updates more than I said I would, and that's on me — it's your call, not mine. Let's keep the two checks we agreed and I'll stay out of the middle. If I'm nervous about something specific, I'll tell you what it is instead of circling."
When they bring every decision back to you
"What would you do if I weren't available? … Good, do that. I'd rather you make that call and be wrong occasionally than wait on me. For this project, that whole category is yours."
What not to do
- —Don't delegate the task and keep the decision. That isn't delegation; it's assigning someone your inbox.
- —Don't request ad hoc updates whenever you feel anxious. Name the anxiety instead, or wait for the check-in you agreed.
- —Don't correct in the final hour. If the direction was wrong, it was wrong at the plan stage and you missed it.
- —Don't take it back the first time it wobbles. Rescue teaches learned helplessness faster than anything else you can do.
- —Don't delegate only the drudgery. If everything you hand off is work you didn't want, people learn that delegation is a dumping mechanism.
Signals you got it right
Decisions get made without you and you hear about them afterward in a sentence. Not a request for approval dressed as an update, but an actual decision with a reason attached.
The plan arrives before you ask for it. People who know what they own bring you the shape of the work early, because they want the correction while it is cheap.
You are surprised by a method you would not have chosen and the outcome is fine. That moment is uncomfortable, and it is the whole point. A team that only ever does it your way has a ceiling exactly as high as your own.
The one thing that changes everything
Say the decision level out loud at handoff — one sentence, every time. 'This one is yours to decide; tell me after.' Managers who do this consistently almost never have micromanagement complaints, because the argument that fuels those complaints is never really about hovering. It's about ambiguity over who gets to decide, resolved in thirty seconds by saying it.
Facing this right now?
Describe your situation and get a diagnosis, one principle, a named protocol, and the exact words to say.
Describe your situation and get a diagnosis →