It was past nine on a Thursday night, and she was still rewriting a report her direct report had already submitted that afternoon. It wasn’t wrong, exactly. It just wasn’t quite how she would have done it, and by the time she’d finished adjusting the phrasing and reordering two sections, she had effectively redone forty minutes of someone else’s work, work she had specifically assigned so it would be off her plate. Her team, meanwhile, had started quietly noticing that anything they submitted tended to come back rewritten, and had begun putting in visibly less effort on first drafts, since the final version was rarely theirs anyway.
This pattern, common among capable, conscientious managers, captures why delegation is so much harder in practice than it sounds in principle. It isn’t a matter of trust in the abstract, or of simply assigning tasks. It’s a matter of tolerating a version of the outcome that differs from the one the manager would have produced themselves, and resisting the urge to close that gap by quietly redoing the work.
What Delegation Actually Requires
Delegation, properly understood, is not simply handing off tasks that a manager doesn’t have time for. It is the deliberate transfer of both responsibility and the authority needed to carry it out, along with a tolerance for outcomes that may differ, sometimes significantly, from what the manager would have produced. Delegating a task while continuing to closely direct every decision within it, or quietly redoing the output afterward, isn’t delegation at all; it’s assignment with an invisible tax, and teams tend to notice the tax even when it isn’t named.
Why Capable Managers Struggle to Let Go
The Belief That It’s Faster to Just Do It Yourself
In the short term, this is often literally true: a manager who has done a task dozens of times can usually complete it faster than someone doing it for the first few times. This short-term math, however, ignores the compounding cost of never building the team’s capability to handle the task independently, which means the manager remains the bottleneck indefinitely.
Perfectionism Disguised as High Standards
Rewriting a “good enough” piece of work to match a manager’s own stylistic preference is frequently framed internally as maintaining quality, when the underlying driver is often a discomfort with any output that isn’t identical to what the manager would have produced themselves.
Fear of Being Blamed for Someone Else’s Mistake
Managers are often held accountable for outcomes regardless of who did the underlying work, which creates a strong incentive to control every detail personally. This fear is legitimate, but it’s usually better addressed through clear checkpoints and appropriate oversight than through avoiding delegation altogether.
Genuine Uncertainty About What Can Safely Be Delegated
Some managers avoid delegating not out of perfectionism but out of a real, unresolved uncertainty about which decisions require their direct involvement and which don’t, particularly in the early stages of managing a new team.
The Real Cost of Under-Delegating
A manager who delegates too little becomes, functionally, the bottleneck for every decision that passes through their team, which limits not just their own capacity but the entire team’s throughput. Team members who are never given genuine ownership tend to disengage over time, doing precisely what’s asked and no more, since initiative that gets quietly rewritten or overridden stops feeling worth the effort. This dynamic is self-reinforcing: less ownership produces lower-quality first attempts, which reinforces the manager’s belief that the team can’t be trusted with more responsibility, which leads to even less delegation. Breaking the cycle requires a deliberate, uncomfortable initial investment in letting outcomes be imperfect while the team builds genuine capability.
A Framework for Delegating Without Losing Control of Outcomes
Effective delegation rests on being explicit about four things at the outset: the specific outcome required, stated clearly enough that success is unambiguous; the boundaries of decision-making authority being transferred, what the person can decide on their own versus what needs a check-in; the checkpoints at which progress will be reviewed, agreed in advance rather than imposed as surprise check-ins; and the standard the final output needs to meet, described in terms of outcome rather than the manager’s own preferred method. This structure allows a manager to stay genuinely informed and maintain real oversight without controlling every step, which is the difference between delegation and abdication on one side, and delegation and micromanagement on the other.
Matching the Level of Delegation to the Person’s Experience
Not every task or every team member is ready for the same degree of delegated authority, and treating delegation as a single, uniform setting tends to produce poor outcomes at both extremes: too much autonomy for someone still building foundational skills leads to costly mistakes, while too little autonomy for someone who has already demonstrated competence breeds frustration and disengagement. A useful approach is to calibrate delegation explicitly, from “do exactly this and check with me before any decision” for a new or unproven task, up through “make the decision and inform me afterward” for someone who has repeatedly demonstrated sound judgment in that specific area. Naming which level applies to a given task, rather than leaving it ambiguous, reduces both the risk of costly independent mistakes and the frustration of being second-guessed on things someone has already proven they can handle.
Tolerating a Different, Still-Good Outcome
Perhaps the hardest part of delegation is tolerating a final result that differs from what the manager would have personally produced, without treating that difference as a defect. A report that reaches the same conclusion through a different structure, or a decision made through a slightly different process, can be entirely sound even though it isn’t the manager’s own version of it. Distinguishing between genuine quality problems, factual errors, missed requirements, poor judgment, and simple stylistic difference is a skill in itself, and it’s often the single biggest lever for a manager who wants to delegate more without lowering actual standards.
Delegating Decisions, Not Just Tasks
Many managers who consider themselves reasonably good at delegating tasks, handing off a report to write, a project to run, still quietly retain nearly all the actual decision-making authority within that task, reviewing and approving each individual choice along the way rather than genuinely delegating the judgment involved. This distinction matters considerably: delegating a task while retaining every decision within it produces most of the burden of delegation, the time spent explaining, reviewing, and correcting, without much of its actual benefit, since the manager remains the bottleneck for every meaningful choice.
Genuinely delegating decisions, not just tasks, means being explicit about which specific choices the person now has standing authority to make on their own, within agreed boundaries, without needing to check in first. This is often the harder half of delegation psychologically, since it requires tolerating decisions made differently than the manager would have made them, in real time, rather than only after the fact. It is also, consistently, the half that produces the most meaningful growth in a team’s independent capability over time.
A Practical Scenario: Breaking the Rewrite Habit
A operations director had a long-standing habit of rewriting nearly every report her team produced before it went to senior leadership, a habit that had quietly become the team’s expectation rather than an exception. She decided to test a different approach with a single report: rather than editing it herself, she returned it with three specific, written questions about gaps she’d noticed, and asked the original author to revise it directly. The revised version wasn’t identical to what she would have written, but it addressed every substantive gap and was, on reflection, genuinely sound. She repeated this pattern deliberately over the following two months, resisting the urge to simply fix things herself even when it would have been faster in the moment. Within a quarter, the average quality of first drafts had visibly improved, not because the team had suddenly become more skilled overnight, but because they were finally being given the chance to close gaps themselves and see the consequences of their own decisions, rather than having every draft quietly absorbed and rewritten before it ever reached them as feedback.
Common Mistakes Managers Make
Delegating the task but not the authority. Assigning work while still requiring approval on every small decision within it produces the frustration of delegation without any of its actual benefits.
Quietly redoing work instead of giving feedback. Rewriting output without explanation teaches a team that their first attempt is never the real deliverable, which quietly lowers effort on future first drafts.
Treating stylistic difference as a quality problem. Conflating “not how I would have done it” with “not good enough” sets an impossible standard that discourages independent judgment.
Delegating everything at once, with no calibration. Handing over full autonomy on an unfamiliar task, without appropriate checkpoints, sets people up to make avoidable, costly mistakes early on.
Action Steps
Before delegating a task, write down the specific outcome required and the boundaries of decision-making authority being transferred, rather than leaving both implicit.
Agree on checkpoints in advance, so oversight happens through planned check-ins rather than surprise intervention partway through.
When output differs from what you would have produced, pause to ask whether it’s a genuine quality problem or simply a stylistic difference before editing it.
Calibrate the level of autonomy explicitly to the person and the task, rather than applying the same default level of oversight to everyone.
Track how often you’re rewriting delegated work rather than giving feedback on it, and treat a high rate as a signal to change your own approach, not just theirs.
Key Takeaways
Delegation requires transferring both responsibility and real decision-making authority; assigning tasks while retaining tight control isn’t delegation.
Under-delegating creates a self-reinforcing cycle: less ownership produces weaker first attempts, which reinforces the belief that more delegation isn’t safe.
Calibrating the level of autonomy to the person and task reduces both the risk of costly mistakes and the frustration of unnecessary oversight.
Tolerating a genuinely sound but different outcome, rather than rewriting it to match personal preference, is often the hardest and most important delegation skill.
Conclusion
Delegation fails, more often than not, not because managers don’t understand its value, but because letting go of control feels riskier in the moment than simply doing the work themselves. The managers who delegate well aren’t the ones with unusually high trust in their teams from day one; they’re the ones willing to tolerate short-term imperfection in exchange for a team that grows more capable over time, and who have learned to tell the difference between a genuine quality problem and a result that simply isn’t their own.
Frequently Asked Questions
How do I delegate to someone who has made mistakes before?
Start with a narrower level of autonomy and clear checkpoints, and expand it deliberately as they demonstrate sound judgment on smaller pieces of the task.
What tasks should never be delegated?
Decisions that carry significant legal, financial, or personnel risk, or that require context only the manager holds, generally warrant closer involvement, though even these can often be partially delegated with appropriate checkpoints.
How do I stop myself from rewriting delegated work?
Before editing, explicitly ask whether the issue is a factual error or missed requirement, versus a stylistic preference; only the former genuinely warrants a rewrite.
What if delegating actually does take more time upfront?
It usually does initially; that upfront cost is the investment that builds a team capable of handling similar work independently in the future.
How much oversight is too much?
If checkpoints happen more often than agreed, or decisions the person was authorized to make are routinely second-guessed, oversight has likely tipped into micromanagement.
How do I know if someone is ready for more autonomy?
Look for a consistent pattern of sound judgment on smaller, similar decisions over time, rather than a single successful instance.
What’s the difference between delegating a task and delegating a decision?
Delegating a task hands off the work itself; delegating a decision hands off genuine authority to choose how that work gets done, within agreed boundaries.