One of the most common tensions in management is delegation that doesn't work.
The manager says they want their team to work autonomously. But then they check in constantly, adjust every output, ask to be copied on everything, or step in at the first sign of difficulty.
The team receives a contradictory message: you have autonomy — but only if you do it exactly as I would.
That's not delegation. That's micromanagement with better intentions.
Why autonomy and control are often confused
Many managers confuse being present with being needed. They confuse checking with caring. They confuse control with quality assurance.
Underneath this confusion, there's often a legitimate concern: what if the team makes a mistake? What if the result is below standard? What if I lose oversight of something critical?
These are real concerns. But the answer isn't tighter control — it's clearer agreements.
The real problem: ambiguity, not lack of trust
When delegation fails, the cause is rarely a trust problem. It's usually an ambiguity problem.
Ambiguity about what "done well" means. Ambiguity about which decisions the person can make independently and which need escalating. Ambiguity about the boundary between support and interference.
In the absence of clear agreements, everyone fills the gaps with their own assumptions. The manager assumes the team knows what level of quality is expected. The team assumes they have more (or less) latitude than they actually do.
Mismatched assumptions create friction. Friction gets interpreted as lack of trust or lack of competence. And the manager pulls the control lever tighter — making the problem worse.
What genuine delegation requires
Effective delegation starts before the task is assigned. It requires defining three things explicitly:
The objective: not just what needs doing, but what "good" looks like. What's the standard? What matters most?
The boundaries: which decisions can the person make independently? Where do they need to check in? What falls outside their remit?
The support: what does the person need from the manager to succeed? Not surveillance — actual support. Removing obstacles, providing resources, being available for genuine questions.
When these three elements are clear, autonomy becomes possible. Without them, it's just an intention with no structure to hold it.
The role of the manager in the middle of the task
Even when the initial agreements are clear, managers often intervene too early — at the first sign of difficulty, before the person has had the chance to find their own solution.
This impulse is understandable. But it has a cost: the team learns to wait for the manager's solution rather than developing their own problem-solving capability.
A useful question to ask before intervening: is this situation genuinely beyond this person's capability, or am I uncomfortable with uncertainty?
Often the honest answer is the second one.
When control is appropriate
None of this means managers should step back entirely. There are situations where closer monitoring is appropriate: high stakes decisions, early stages of new roles, genuine skill gaps, or contexts where errors have serious consequences.
The point isn't to abandon control. It's to use it intentionally — as a deliberate choice based on the specific situation — rather than as a default response to anxiety.
Practical steps
Before the next delegation conversation, it's worth asking: have I been explicit about what "good" looks like? Have I defined which decisions this person can make independently? Have I been clear about when and how I'd like to be involved — and why?
And after: am I intervening because something is genuinely at risk, or because I'm uncomfortable not being in control?
These aren't comfortable questions. But they're the ones that separate managers who build team capability from those who inadvertently prevent it.