Start with a clear outcome
Before handing work over, ask:
“What exactly needs to be true when this is finished?”
Not:
“Sort this out.”
Not:
“Have a look at this.”
Clear outcome. Clear destination.
Define what good looks like
The manager needs to explain: quality; timing; customer impact; commercial boundaries; non-negotiables. If the standard is vague, the manager will feel compelled to keep checking. Clarity reduces anxiety.
Clarify what is theirs to decide
This is critical. What can they decide without asking? What needs consultation? What needs escalation? If those boundaries are unclear, either: the employee keeps asking permission; or the manager keeps checking because they fear surprise. Neither is useful.
Agree the review point
Do this before the work starts.
“Let’s review this on Thursday at 2pm.”
Now the manager knows there is a structured return point. That makes it much easier not to interrupt beforehand.
Review points are not micromanagement
They are part of good delegation. The issue is not whether you check. It is whether checking is: predictable; proportionate; purposeful.
Stop using random check-ins
Random messages like:
“Just checking where this is up to…”
five times a week create noise. Better to agree the rhythm in advance.
Match the review frequency to risk
High-risk work may need tighter checkpoints. Low-risk work may need very little. The level of oversight should reflect: consequence; complexity; capability; experience. Not manager anxiety alone.
Ask yourself what you are actually worried about
Quality? Deadline? Cost? Customer? Reputation? Then build visibility around that. Do not monitor everything. Monitor what matters.
Use milestones
For longer work, agree intermediate points. For example: first draft Friday; customer confirmation Tuesday; final completion Thursday. Now progress is visible without daily hovering.
Ask for evidence, not reassurance
“How is it going?”
“Fine.”
Not very useful. Better:
“What is complete?”
“What remains?”
“What is at risk?”
Evidence creates better visibility.
Ask for the person's plan
Before they start:
“Talk me through how you’re going to approach this.”
This is one of the best anti-micromanagement tools. You can hear the thinking. Spot gaps. Clarify assumptions. Then let them execute.
Do not turn that into dictating every step
If their approach is sensible, let them use it. Different does not mean wrong.
Separate outcome from preference
Ask:
“Does this genuinely affect the result?”
If not, perhaps it is merely your preferred way of doing it. Managers often over-control preferences.
Stop rewriting good work into your style
Employee delivers something acceptable. Manager edits endlessly. Why? Because:
“That’s not how I would have written it.”
That teaches the employee that ownership is fictional.
Use standards where standards matter
Safety. Legal. Brand. Quality. Fine. Be explicit. Everything else may allow flexibility.
Agree what needs escalation
For example: deadline at risk; customer issue above threshold; cost exceeding limit; unexpected safety or legal concern. Then the employee knows when to raise something.
Early escalation builds trust
You can give more freedom when you know the person will raise risk early. That is part of the bargain.
Tell them what you do not need to know
This is surprisingly helpful.
“I don’t need a running commentary. I do need to know if X changes.”
That creates space.
Do not ask to be copied into everything
Email visibility can feel like control. Usually it becomes noise. Ask:
“Do I need to see this, or do I need to know only if something goes wrong?”
Use exception-based management
If everything is on track, let it run. If something moves outside agreed parameters, bring it forward. That scales much better.
Trust is not blind
Delegation is not:
“Off you go and I hope for the best.”
It is: clear outcome; appropriate authority; useful evidence; agreed review; follow-through. That is structured trust.
Build trust through delivery
If the person consistently delivers: give more room. If they raise risk early: give more room. If they use good judgement: give more room. Autonomy should grow from evidence.
New employees may need more structure
That is normal. They are learning: the work; the business; your standards. More check-ins may be appropriate at first.
Reduce oversight as capability grows
This is important. Do not keep supervising an experienced, reliable person like a beginner. That becomes frustrating and unnecessary.
Tell people when autonomy increases
“You’ve handled this consistently well, so I don’t need the midpoint check anymore.”
That reinforces progress.
Do not punish the first mistake by taking everything back
A mistake happens. Manager says:
“I knew I should have done it myself.”
No. Ask: What happened? Was the reasoning sensible? What was learned? Then decide what needs changing.
Distinguish recoverable from high-consequence mistakes
Some decisions deserve more oversight. That is okay. Good delegation is not reckless.
Teach people to self-check
Before bringing work back, ask them:
“What have you checked?”
“What do you think could be wrong?”
This builds their own quality control.
Ask for a recommendation, not a question
If they hit a problem:
“What do you recommend?”
That keeps thinking with them.
Do not let every obstacle boomerang the task back
Someone says:
“I’m stuck.”
Do not automatically say:
“Give it to me.”
Ask where they are stuck. Support that piece. Then return ownership.
Support is not taking over
This distinction is everything. You can provide: context; access; decision; coaching. Without owning the task.
Use a simple delegation agreement
Before handing something over, cover: Outcome What needs to be achieved? Standard What does good look like? Authority What can they decide? Risk What matters most? Escalation What needs to come back early? Review When will you check progress? Completion What proves it is done? That removes a lot of ambiguity.
Do not delegate only verbally if the work matters
For significant work, write the key points down. Not a 14-page procedure. Just enough to keep the bargain visible.
Use the Action Register where appropriate
Owner. Action. Due date. Status. Now the manager does not need to keep it in their head.
Let the system remember
The manager should not be carrying:
“I must remember to ask…”
all week. That is what visible commitments are for.
Good delegation includes follow-through
At the agreed review: What happened? What changed? What needs attention? That is management.
Close completed work
Do not keep old actions hanging around. Done means done. Close it. That keeps the system clean.
If the work is at risk, renegotiate consciously
Do not let the date silently drift. What changed? What is the new commitment? Who is affected? That preserves accountability.
Do not penalise early warning
If someone says early: “I’m at risk,” do not punish them for telling you. Work the issue. Otherwise next time they may hide it. But challenge repeated poor planning Early warning is useful. Repeatedly creating the same risk is still a performance issue. Both things can be true.
Avoid the shadow-manager problem
You delegate. Then secretly keep solving it behind the scenes. You contact the customer. Check the numbers. Give instructions around the employee. That destroys ownership.
If you delegate, delegate
If you cannot genuinely let go yet, perhaps the task is not ready to move. Then be honest.
Ask whether you have built enough capability
Maybe the employee genuinely is not ready. Fine. What needs developing? Use staged delegation.
Use the delegation ladder
Stage 1 — I do, you watch
Learning.
Stage 2 — We do together
Practice.
Stage 3 — You do, I review closely
Developing independence.
Stage 4 — You do, I review by exception
More freedom.
Stage 5 — You own it
Full responsibility within boundaries. That creates progression.
Do not leave people permanently at Stage 3
If they are capable, move them. Otherwise the manager becomes the bottleneck.
Ask who is holding the pen
This is a useful metaphor. Who is actually doing the work? If the manager keeps grabbing the pen back, ownership has not transferred.
Delegate decisions too
Managers often delegate tasks but keep all decisions. That limits development. Give decision authority where appropriate.
Clarify consequences
If they make the decision, they should own the result. That builds judgement.
Debrief decisions
“What worked?”
“What would you do differently?”
That helps people learn without requiring constant pre-approval.
Avoid approval culture
If every tiny decision requires manager sign-off, delegation becomes fake. You have delegated activity, not authority.
Use thresholds
For example: you can approve up to X; discount within Y; resolve customer issues within Z. Clear boundaries create freedom.
Review the thresholds as capability grows
What once needed approval may no longer need it. That is organisational progress.
Watch for manager anxiety
Sometimes the employee is performing well. The manager still checks constantly. Then the problem may sit with the manager. Why do they need to know every detail? Fear? Identity? Lack of trust? Control habit? That needs development too.
Ask the manager what evidence would make them comfortable
Then build that evidence into the system. Much better than hovering.
Do not turn visibility into surveillance
Visibility:
“Show me the agreed evidence at the agreed time.”
Surveillance:
“I need to know what you’re doing all day.”
Very different.
Watch the language
Micromanaging language:
“Have you done this yet?”
“What are you doing now?”
“Send me everything.”
Accountability language:
“We agreed Thursday. Is anything at risk?”
The second is calmer.
Let people own their method
Within agreed boundaries. Ownership needs room.
Ask what would happen if you stopped checking
This is useful. If the answer is: “They would probably still deliver,” then perhaps the checking is for you, not them. Test it Remove one unnecessary check. See what happens.
Use missed outcomes as evidence
If the work fails: do not immediately increase all surveillance. Diagnose. What failed? Clarity? Capability? Authority? Effort? Improve the right thing.
Do not respond to one person's failure by micromanaging everyone
This is common. One employee misses. Manager creates a new control for the entire team. Be careful. Solve the actual problem.
Keep control proportional
Strong performers should feel trusted. Developing performers should receive support. Repeatedly unreliable performers may need closer management. That is reasonable.
Make the bargain explicit
A useful conversation is:
“I want to give you as much autonomy as I reasonably can. In return, I need you to keep commitments, raise risk early and tell me if something moves outside the agreed boundaries.”
That is a mature delegation bargain.
Reliability creates freedom
People who are reliable need less checking. This is one of the rewards of doing what you said you would do.
Managers need to model reliability too
If you expect employees to honour commitments, you need to do the same. Trust runs both ways.
Do not cancel review points constantly
If you agreed to review Thursday, review Thursday. Otherwise the system becomes unreliable.
Use one-on-ones for broader delegation development
What are they ready to own next? Where are they still dependent? What decision can move down? That builds capability systematically.
Ask what no longer needs your involvement
This is an excellent management question. If the answer keeps growing, delegation is working.
A practical anti-micromanagement test
Before checking, ask: Did we agree a review point? If yes, can it wait? Is there a genuine new risk? If no, why am I checking? Do I need evidence or reassurance? Be honest. Have they given me reason not to trust the process? Use evidence. Is this high-consequence? More oversight may be justified.
Am I checking the outcome or controlling the method? Important distinction. Could a better measure replace my interruption? Often yes.
A practical delegation conversation
You might say:
“You own this outcome. This is what good looks like. You can make these decisions yourself. I need you to raise X or Y immediately. Otherwise, let’s review progress on Thursday. If nothing is at risk before then, you don’t need to update me.”
That is clear. And liberating.
One final question
Ask:
“Have I built enough clarity into this delegation that I can reasonably leave the person alone until the agreed review point?”
If the answer is no, improve the delegation. If the answer is yes, leave them alone. Because the answer to constant checking is not blind trust. It is better management design. Clear outcome. Clear standard. Clear authority. Clear escalation. Clear review. Then let people work. That is how you retain control without becoming the person standing over everybody's shoulder.
