How to Delegate Without Micromanaging (For Recovering Control Enthusiasts)

Fernanda: Let's talk about something that quietly derails a lot of good managers: delegation. Not the concept—you know what delegation is—but the actual doing of it. Trusting someone else with something that matters, letting go of how you would do it, and not hovering over their shoulder every five minutes—that part is where it gets hard.

If you've ever said, "It's just faster if I do it myself," or if you've taken something back from someone because it wasn't going quite right, or found yourself working late on tasks that technically weren't even yours anymore, this video is for you. I'm Fernanda, and I work with managers and organizations on people development. I've coached leaders across industries, across cultures, and across every flavor of delegation struggle that you can imagine.

Today, I'm going to walk you through why this is so hard, what it's actually costing you and your team, and a practical framework that you can start using right away. Let's get into it.

First, let's name what's actually going on, because "I'm a control freak" is rarely the whole story. Reason number one is fear of losing quality. You have a standard, you know what good looks like, and handing something off feels like gambling with that standard. What if it comes back wrong? What if it reflects badly on you?

Reason number two: "It will be faster if I do it." This one is sneaky because it's true in the short term. You can write that report faster than you can explain how to write it. So you do it yourself, and then you do it again next week, and the week after that. Now you've built a system where you are permanently the bottleneck.

Reason number three: not wanting to burden the team. This is the one nobody talks about enough. A lot of managers, especially empathetic ones, hold back because they don't want to pile more on someone who already looks busy. The intention is kind, but what it's actually doing is keeping your team from growing and keeping the manager drowning.

Reason number four: fear of what happens when someone does it differently. It's not wrong; it's just different. Somehow, that feels almost harder to accept than an actual mistake.

Reason number five: perfectionism doing a very convincing impression of high standards. There's a difference between having standards and being unable to release control unless something is done exactly your way. One makes you a leader; the other makes you a bottleneck.

Do any of those sound familiar? Because they should. Most of us have lived in at least one of these, and some of us have lived in all five at the same time.

Here's the part that people underestimate: the cost isn't just your stress level, though that matters, too. When you don't delegate, or if you delegate and then hover, the cost spreads. It spreads to you because you stay stuck doing work that isn't at your level, you don't have space to think strategically, and you burn out. At some point, your capacity becomes your team's ceiling.

It also spreads to your team. People don't get to stretch, take ownership of meaningful work, or fail safely and learn from it. Over time, they stop trying to bring their best thinking because they've learned it won't be trusted anyway.

Adam Grant talks about how the best managers build capacity in others, not just output. When you over-function, you under-develop the people around you. That's not a small thing—that's the difference between a team that needs you for everything and a team that grows beyond what you imagined.

Engagement research backs this up. Gallup consistently finds that autonomy—feeling trusted to do your work—is one of the strongest predictors of employee engagement. When people don't feel trusted, they disengage, and your strongest people start looking for environments where they can actually step up. So the question isn't, "Can I do it faster myself?" The question is, "What does it cost everyone if I do?"

Let's talk about how to actually do this well, because delegation isn't just handing something off; done right, it's a development conversation. Here's a simple framework I use with managers called Set, Support, Receive.

Step one: Set clear expectations before you hand anything off. This is where most delegation falls apart. A manager tosses something over the fence with vague instructions, the team member does their best, it comes back not quite right, and then the manager thinks, "See? This is why I just do it myself."

Before you delegate anything, get clear on what "done" looks like—not how to get there, but what the outcome should be, what the deadline is, and what the checkpoints are along the way. Clarify what level of autonomy this person has: can they make decisions independently, or do they need to loop you in at certain points? What resources do they have access to?

Here's a step most managers skip: check for understanding. Don't just ask, "Does that make sense?" because almost everyone says yes. Ask them to reflect back what they're going to do—not to quiz them, but to make sure you're aligned before they spend three days going in the wrong direction.

Step two: Support by giving autonomy with a safety net. This is the piece that separates delegation from abandonment. Once you've handed something off, your job is not to disappear; it's to be available without hovering. There's a big difference.

Ken Blanchard's Situational Leadership model is really useful here. The level of support someone needs depends on two things: their skill level and their confidence. A new team member doing something for the first time needs more guidance, whereas a seasoned person doing something in their wheelhouse needs you to mostly get out of the way.

Your job is to read which situation you're in and calibrate accordingly. A simple check-in works well here, such as: "I'll leave you to run with this, and let's touch base on Thursday just to see where you are—not to review, just to answer any questions." That's not micromanaging; that's support with a light touch.

Step three: Receive the work with openness. This is the part nobody puts in a delegation framework, but it might be the most important one. When work comes back, your first job is not to evaluate it against how you would have done it; your first job is to evaluate it against the outcomes you agreed on in step one.

Did they meet the brief? Is the work good enough to move forward, even if it's not exactly how you would have done it? If yes, let it go and let their version be their version.

If it needs revision, great—this is where the development actually happens. Give the "why" behind the changes, not just the "what," and send it back to them to revise. Resist the urge to just fix it yourself; that moment when they rework it and get it right is the whole point.

Michael Bungay Stanier has a great question in The Coaching Habit that's worth keeping in your back pocket: "What kind of support are you looking for?" It sounds simple, but it stops you from jumping in with advice or taking over when what the person actually needed was just a sounding board.

Let's talk about the moment that trips up even well-meaning managers: someone does the work, and it's fine—it might even be good—but it's not how you would have done it. It has a different format, approach, or sequence, and something in you just wants to say, "Actually, can you just do it like this instead?"

Here is the question to sit with first: is this a quality issue or a preference issue? Quality issues are real. If something is inaccurate, incomplete, or doesn't meet the agreed-upon outcome, that's feedback territory, and you give it.

Preference issues are different. If the work meets the brief but just doesn't look like yours, that's information about you; it's not a problem with them. Consider that sometimes their way is actually better, and a fresh perspective can produce something you wouldn't have thought of. That only happens if you give people space to bring their own thinking.

Now, what if someone genuinely struggles and the work keeps coming back needing major revisions? That's not a delegation failure; that's a developmental signal. It means the person needs more coaching, more support, or more scaffolding before they can own that type of work independently.

You adjust your approach—you don't just take the task back permanently and call it a day. Brené Brown talks about "clear is kind." Vague delegation followed by disappointment when someone doesn't read your mind isn't fair to anyone. Clarity upfront, specific feedback when needed, and patience with the process: that's what good delegation looks like in practice.

Delegation is a skill, not a personality trait. It's not something you either have or you don't; it's something you learn, practice, and get better at, and your team will feel the impact immediately when you do.

Here's what I want to leave you with: start small. Take one task this week that you've been holding on to and ask yourself: "Could someone else do this? Could it be a growth opportunity for them?" If the answer is yes, use the Set, Support, and Receive framework and try it. You don't have to be perfect at this; you just have to start.

If you want to go deeper on this, delegation is one of the core modules in the work I do with organizations to build this kind of capability at scale. One manager learning to delegate better is great, but a whole team of managers doing it changes the culture. If that's something you would like to explore, the link is in the description—let's talk.

If this video was useful, share it with a manager you know who needs it; it might be the nudge they didn't know they were waiting for. I'll see you on the next one.

Fernanda Brasileiro

People Development Consultant & Strategist

CONNECT

© 2026. All rights reserved.

Services

About

Set up a free consultation

GET FREE DIAGNOSTIC