← Back to Insights February 24, 2025

Delegation Is Not a Management Trick - It's How Work Gets Done

By Lauren Humphrey · 8 min read

Managers who don't delegate effectively are not managing - they're doing two jobs. Their own and someone else's. This is inefficient at the individual level and corrosive at the team level: direct reports who never get real ownership don't develop, and a team where the manager does all the hard work doesn't build the collective capacity to function without constant intervention.

Delegation failure comes in three forms: under-delegating (keeping too much), over-delegating (dumping without context), and incomplete delegating (handing off the task but not the authority to make decisions about it). The third is the most common and the least recognized.

The Task-Authority Gap

Incomplete delegation looks like this: a manager tells a direct report to own a vendor negotiation, but then weighs in on every email, reverses decisions already made, and needs to approve each step before the direct report can move. The direct report has the task but not the authority. They are executing while the manager is still deciding.

This creates a specific kind of frustration. The direct report can't move quickly because every decision routes through the manager. The manager is still involved in the work at a level of detail they didn't intend. The stated goal - freeing up the manager's time and developing the direct report - is achieved by neither party. The work takes longer and nobody grows.

Effective delegation requires specifying two things at handoff: what the person is accountable for producing, and what decisions they can make independently. Without that clarity, the direct report defaults to checking in on everything (to avoid making a wrong call) or acting without input (and getting reversed), depending on their personality. Neither outcome is what the manager wanted.

The Delegation Ladder

A useful model for calibrating delegation is what organizational development researchers often call the authority ladder - a spectrum of how much decision-making authority accompanies a task assignment. At one end: "gather information and bring it back to me." At the other end: "handle it completely and let me know what happened." Most managers operate in a narrow band in the middle and don't vary it based on the direct report's experience with the specific task type.

The right delegation level depends on two variables: the stakes of the decision and the direct report's track record with similar decisions. High stakes, low track record - delegate the execution but keep the decision authority, and build track record over time. Low stakes, high track record - delegate fully, don't check in until they're done. The error most managers make is applying the same level of oversight to all work regardless of stakes or track record.

Managers who only delegate low-stakes tasks never build the high-stakes track record that would let them delegate the important work. Teams in this pattern tend to be highly dependent and feel micromanaged even when the manager thinks they're delegating heavily.

How to Delegate a Task Properly

The handoff conversation is where most delegation breaks down. It's usually too brief. The manager says "can you take point on X?" and the direct report says yes and neither party is certain they're thinking about the same thing.

A complete delegation conversation covers five items. First, the outcome: what does done look like? Not the tasks - the result. "We need a recommendation for which analytics vendor to use by March 15, with a clear rationale for why" is an outcome. "Research some analytics vendors" is a task list with no defined finish line.

Second, the constraints: what can't change? Deadlines, budget limits, non-negotiable requirements. These aren't micromanagement - they're the actual parameters of the problem. A direct report who doesn't know the constraints will solve the wrong problem efficiently.

Third, the decision authority: what can they decide alone? What needs sign-off? Being specific here prevents the check-in loop that makes delegation feel like supervision in disguise.

Fourth, the resources: who can they talk to, what information do they have access to, is there a budget?

Fifth, the check-in cadence: not constant monitoring, but a pre-agreed moment to assess progress and surface blockers before they become failures. "Let me know by the 10th if anything looks unclear" gives the direct report enough runway while keeping the manager informed at a meaningful checkpoint.

Delegating Stretch Assignments

Some delegation is about distributing work efficiently. Some is about deliberate development - giving a direct report a task that stretches their current capability. These two types require different handling.

For stretch assignments, the manager needs to be explicit: "This is a stretch. You haven't done this exact type of work before. I'm giving it to you because I think you can handle it and because it will build a skill you need. I'll be more involved as you find your footing." That framing prevents the direct report from feeling set up to fail and gives the manager a reason to be present in the work without it feeling like hovering.

The growth opportunities in stretch assignments are specific. A developer managing their first cross-functional project will struggle with stakeholder alignment - the technical work will be fine. Knowing which capability is being stretched allows the manager to target support precisely rather than monitoring the whole engagement.

Reversing Decisions Without Undermining Ownership

Sometimes a manager delegates, the direct report makes a decision, and the manager disagrees with it. How this situation is handled determines whether the delegation was real or performative.

Reversing a delegated decision is sometimes necessary. A client relationship might be at risk. A process might have a legal implication the direct report wasn't aware of. The reversal is legitimate. What matters is how it's communicated. "I made a mistake in not flagging this constraint at the start. Here's the information that changes the decision, and here's why I'm making a different call" is very different from "I looked at this and I'm going in a different direction." The first models ownership. The second teaches the direct report that their decisions can be overridden at any time for any reason, which is functionally equivalent to having no authority at all.

Building a Delegation Practice Over Time

Managers who delegate well at the organizational level - not just as a tactical tool - treat ownership development as an explicit part of their job. They track which direct reports have taken which kinds of responsibility, where the gaps are, and what's next. They build ownership systematically rather than ad hoc.

This level of intentionality pays dividends specifically during the manager's absence. Teams with well-developed ownership continue functioning well when the manager is out or moves on. Teams where the manager kept all the decision-making authority experience a sharp decline in effectiveness when that manager isn't there.

If you're thinking about how delegation connects to the broader development of your direct reports, read our guide on the first 60 days as a new manager - the foundation you build early determines how much ownership your team can hold later.