What is the difference between delegation and micromanagement?

The difference is when the check-in is agreed. In delegation the outcome and the checkpoint are set up front and the method is left alone. In micromanagement the work is handed over but taken back the moment a decision is made: the approach is corrected, the output rewritten. After that the person stops taking initiative, because they have learned it does not survive.

How do you escape the I could do it faster myself trap?

Do the arithmetic over repetitions rather than a single instance. A ten-minute task done five times a month costs six hours a year; if teaching it takes an hour, you break even in the second month. And the real cost is not time: as long as the task stays with you, you remain a single point of failure.

What if delegated work goes badly?

Taking the work back should be the last resort; every reclaimed task teaches the team not to volunteer again. Move the checkpoint earlier, refresh the context, and if needed drop a level explicitly rather than silently. If the outcome is bad, the responsibility stays with the manager: that is part of the definition of delegation.

Home → Leadership

Delegation: Letting Go of the Outcome, Not Handing Out Tasks

You handed the work over. Then you thought you would "just take a look". Then you wrote your own version and sent it across as "you could also do it this way". A week later the person asks: "How would you like it done?" That question is the receipt for a delegation that never happened.

Sertaç Yıldırım · 12 April 2026, 20:25 · 5 min read

In short

Responsibility without authority is not delegation. No decision rights means no handover.
"I could do it in ten minutes" is the wrong sum. The right one is ten minutes × times per year.
Set a checkpoint; don't hover. Following up is not interfering.
If the outcome is bad, it is on you. That is not a risk, it is the definition.

From the field: ten minutes that lasted eight months

For a while I ran the data migration step before every release myself. The reasoning was sound: it took ten minutes, I did it in two, and doing it wrong could corrupt a table. Explaining it would take half an hour; doing it took two minutes.

Eight months later I went on holiday in August. That week the release slipped. Someone tried, could not be sure, and chose to wait — entirely the right call, because there was nothing written down.

The arithmetic afterwards: roughly forty runs in eight months, two minutes each, eighty minutes. Teaching it would have cost thirty. I had broken even in month two, and the remaining six months were pure loss. And the real loss was not time; it was a team that depended on one person for a release step.

"I could do it faster" is a true sentence. It is only true once, and no task is ever done once.

Authority ships with responsibility

This is where delegation nearly always breaks. "You own this now," we say, while every decision still routes through the manager. The person is accountable but powerless: waiting for approval at each step, and blamed for the delay.

Saying three things in one sentence fixes it: what I am handing over, which decisions are yours, and where the boundary is.

Vague handover

"Take over the reporting work, and come to me if you get stuck."

Result: they bring every decision to you, because they cannot tell how far their authority reaches. And if one unasked decision gets reversed, they learn to ask about everything forever.

Bounded handover

"Reporting is yours now. Library choice, data model and timing are your calls — no need to check with me. Come to me on two things: if it costs more than $500 a month, or if customer data leaves for another service. Let's sit for twenty minutes in two weeks and see where it is."

Result: clear decision space, clear boundary, checkpoint agreed in advance.

Five levels of handover

Delegation is a dial, not a switch. Giving the same person different levels on different tasks is perfectly normal; the mistake is not saying which level.

Level	The sentence	When
1	"Do it this way."	New joiner, risky and hard to undo
2	"Research it, bring it to me, we decide together."	New to the area
3	"Decide, tell me before you act."	Trust is being built
4	"Decide, act, tell me after."	The normal case
5	"This area is yours; you don't need to tell me."	Full ownership

Most friction comes from a mismatch: the manager thinks they are at level 3, the engineer thinks they are at 5. Then a decision gets reversed and both sides feel wronged. Naming the level in one sentence removes the entire problem.

Following up is not interfering

Treating delegation as "handed over, forgotten" is the other failure — that is abandonment, not delegation. The difference is when the checkpoint was set:

Agreed in advance creates safety: "we'll look in two weeks" means the two weeks can be worked calmly.
Arriving unannounced destroys it: "just checking how it's going" plants "am I doing this wrong?" every time.

The phrasing matters too. "Why did you do it that way?" produces defence; "what were you weighing when you chose that?" opens the reasoning. Both ask for the same information, but only one puts the person on trial.

When it goes badly

It will. Some of what you delegate will turn out worse than you would have done it; that is not an accident, it is the tuition you are paying.

Hard rule

Do not take the work back. Reclaimed work becomes work nobody volunteers for; the team learns that "he ends up doing it anyway" and initiative dies. Tighten the checkpoint, refresh the context, drop a level if you must — but say so out loud.

Outward, there is one rule: if the outcome is bad, it is yours. "I had given it to them" is the most expensive sentence a manager can say; the moment it is said, the team learns nobody is standing behind them.

Checklist

Before handing work over

Can I say in one sentence what I am delegating?
Did I say which decisions they can make without me?
Did I state the boundary (budget, data, irreversible steps)?
Did I put the checkpoint on the calendar in advance?
What happens if I don't ask about it for a week? (If the answer is "disaster", the boundary is missing.)
If the outcome is bad, whose name will I say outside the team?

Conclusion

Delegation is not a time-management technique; it is the measure of how well your team runs without you. The simplest test: if you disappeared for a week, what would stop? Every line on that list is work you have not delegated yet.

The funny part is that shortening the list does not make the manager redundant. It is the only way the manager gets time for the actual job: direction, people, priorities.