How to Delegate Without Losing Control

I have a theory about why managers don't delegate, it's not that they don't trust their people. Most managers do trust their people. The real issue is that delegation creates a specific kind of anxiety that doesn't have a name. It's the feeling of being accountable for an outcome you can no longer see. You handed off the work, and now it's happening somewhere you can't observe, and you still own the result if it goes sideways.

That anxiety is completely rational. The fix, though, isn't to stop delegating. The fix is to build a system that gives you visibility without requiring you to hover. Most managers never build that system. Instead they either hold on to everything, or they hand things off and then quietly worry all week while ping-checking for updates.

Andy Grove wrote in High Output Management that a manager's output is the output of their team, not their individual work. I read that early in my career and agreed with it intellectually. It took me longer to actually live it, because living it meant letting things go, and letting things go felt like losing control. What I eventually figured out is that the feeling of control and actual control are different things. Hovering feels like control. A clear handoff with a check-in structure is actual control.

Neither of those approaches works. Here's what does.

The four categories worth delegating

Not everything should be delegated. I've seen managers try to hand off things they shouldn't: decisions that require their authority, conversations that need their specific relationship, anything where the delegation itself would send the wrong signal. The goal is to be deliberate about what leaves your plate, not to just reduce your workload.

Here are the four categories I think about:

1. Routine tasks you keep doing out of habit. These are things you've done so many times they feel automatic. You're not learning from them, you're not uniquely positioned to do them, and they're eating time you could spend on decisions only you can make. If you've done something more than three times and it's the same each time, it's a candidate for delegation.

2. Growth assignments for your team. These are tasks that would stretch someone on your team, things a little above where they're comfortable, that require them to figure something out. Delegation here isn't about offloading; it's about intentional development. The cost is that it'll take longer and might be messier than if you did it yourself. That's the point.

3. Things others can do better than you. This one stings a little. There are people on your team who are better at certain things than you are. If you're still holding those things because letting go feels like admitting something, that's ego, not management. Hand it off.

4. Things that free you for strategy. Every hour you spend on execution is an hour you're not spending on the decisions, conversations, and planning that only you can do. If you're a manager who's still buried in individual-contributor work, you're probably the bottleneck on your own team's progress.

"Delegation isn't giving something away. It's choosing who owns the outcome, then building the system that makes that ownership real."

The handoff conversation most managers skip

This is where almost every delegation failure starts. Most managers hand off work like this: "Hey, can you take care of X? Let me know if you have questions." Then they walk away and wonder why it didn't go the way they expected.

The problem is not the person they handed it to. The problem is an incomplete handoff.

I learned this the expensive way. I delegated the monthly reporting process to a team member, handed her the template, told her it needed to go out by the 15th. She sent it. I opened it and realized the format was completely different from what I'd expected, and two sections I considered mandatory were missing. Neither of us had done anything wrong. I'd just never told her what done looked like, and she'd made reasonable assumptions. We both lost a day fixing it.

There's a 10-minute conversation that should happen every time you delegate something meaningful. Not a long meeting, just a real conversation that covers the things most managers assume are obvious but aren't.

Here's the five-step handoff conversation I use:

1. Define what done looks like. Not "I need this handled." An actual description of the end state. What will be true when this is complete? What quality standard are you expecting? "Good job" is not a success metric. Be specific enough that they could know, without asking you, whether they've hit it.

2. Clarify decision boundaries. What can they decide on their own? What needs to come back to you? This is the part that trips people up the most. If you haven't explicitly said "you don't need to check with me on vendor selection, but anything over $2k needs my sign-off," you'll either get too many check-ins (because they're being cautious) or too few (because they assumed autonomy you didn't intend to give).

3. Set up the check-in structure. How often do you want updates? Is it a weekly Slack note? A quick line in your 1:1? Exception-only (only surface it if something's blocking)? Get explicit. If you don't, people default to whatever feels right to them, which may not match what you need.

4. Surface the likely hard part. Ask: "What's the thing most likely to make this harder than expected?" Sometimes they'll tell you something you didn't know. Sometimes this question surfaces a constraint you both overlooked. And it shows you're not just dumping work. You're thinking about what they're walking into.

5. Make it safe to come back early. Say explicitly: "If something's not going the way we expected, I want to know early, not late. Coming to me with a problem before it's critical is the right call." This changes how people think about escalation. Most employees default to not flagging problems because they're worried it looks like failure. Giving them explicit permission to come back early changes that.

Common mistake: Delegating the task but keeping the worry. You hand it off, then spend the rest of the week checking Slack for updates, drafting the version you would have done, and quietly second-guessing every decision they make. That's not delegation. It's doing the work twice. If you can't let go of the anxiety, the fix is better visibility, not more checking in.

How to check in without micromanaging

Here's the honest truth about micromanagement, it almost always comes from missing visibility, not from a character flaw. When you can't see what's happening, you fill the gap with check-ins. Then more check-ins. Then you're that manager, not because you wanted to be, but because you didn't build an alternative.

Liz Wiseman describes something similar in Multipliers, where she explains how well-intentioned managers accidentally create dependency by staying too involved. The team stops developing its own judgment because the manager's presence signals that their judgment is the one that counts. The micromanager and the accidental diminisher are often the same person.

The alternative is simple: a visible, low-friction status system. It doesn't have to be sophisticated. You just need answers to three questions at any moment:

• What did I delegate, and to whom?
• What's the current status: on track, needs attention, or stuck?
• Is there anything that requires my input before the next check-in?

If your team updates that list once a week, even just a quick line, you don't need to ask. You already know. The check-in becomes unnecessary, and the micromanagement anxiety goes away because you have actual information instead of silence.

"Micromanagement is almost always a symptom of missing visibility. Build the system that makes the check-in unnecessary, and the behavior fixes itself."

What to keep on your own plate

Some things shouldn't be delegated. Not because you can't trust people, but because some decisions carry organizational weight or relational consequences that require your specific authority and context. Here's what I generally keep:

• Performance conversations. These need to come from you. Delegating a difficult feedback conversation sends the message that you don't have the courage for it yourself.
• Hiring decisions. You can involve your team in interviews, but the decision to bring someone in or not is yours.
• Decisions that set precedent. If something will affect how the whole team works, or signals something about values and expectations, it usually needs to come from you.
• Things that require your specific relationships. If a conversation needs to happen because of your relationship with a stakeholder, a peer, or someone senior, hand-off dilutes it.

The real question: If you stayed home sick tomorrow, which things on your plate would genuinely stop or slow without you, and which ones would just continue? Everything in the second category is a delegation candidate. Everything in the first is where your time should actually be.

Delegation done right isn't about letting go of accountability. It's about expanding how much your team can move without requiring you to be the bottleneck. The manager who's figured this out isn't less in control. They're more in control, because what they can see and influence just got bigger. That's what I was trying to build when I built Cadence: a way to delegate confidently because you can see the status without asking, and your team knows exactly what done looks like.

Make delegation trackable.

Cadence lets you track what you've delegated, see status at a glance, and stop second-guessing what's happening on your team. 14-day free trial.