I sit in rooms with leaders who delegate to team members yet say “it’s yours” while continuing to monitor, correct, and redo the work. The assignment is real, but the autonomy is not. They’re convinced they’re protecting quality; however, what they’re really doing is preventing judgment and teaching learned helplessness.
This is what I call the “delegation lie”, and it’s pervasive in leadership.
There’s this gap between what we say we’re doing and what’s actually happening, and it’s wide enough to park someone’s entire professional career lifespan in. When we delegate authority while retaining decision-making authority, what we are really doing is handing off work while keeping surveillance on. We assign responsibility while making clear that nothing they do will really be enough until we’ve redone it. Afterward, we wonder why our teams stop thinking for themselves.
I’m not convinced that the problem is that our standards are too high; rather, it may be that with all of the constant correction, our team has learned that compliance is what we actually value.
How Constant Correction and Rework Destroy Employee Trust
I watched this play out in real time years ago. A leader I worked with would delegate a project to a direct report, give clear instructions, and then show up three days into a two-week timeline asking for updates. It wasn’t because something was going wrong, but rather because being in control felt like protection. The leader would find something to adjust, feedback would flow down, and the employee would shift course. Two days later, another check-in, and yet another adjustment.
By day ten, the employee just stopped thinking about what made sense for the project. They were thinking about what the leader wanted to see. By day fourteen, when the work landed, the leader reviewed it, found gaps, and redid significant portions of it before sending it to the client.
That employee ultimately left the company, not because the work was hard, but because they’d stopped feeling they had anything to contribute.
What is Learned Helplessness in Leadership?
There’s research behind this. Psychologist Martin Seligman’s work on learned helplessness showed that when people are repeatedly told their actions don’t matter because someone else will change them anyway, they stop trying to act; they become passive, wait for direction, and ultimately develop learned helplessness. It is not because they lack ability but because they’ve learned their ability doesn’t matter in this context.
In a delegated context, this is exactly what constant correction produces. Every time a leader redoes delegated work, the message the team receives isn’t “do better”; it’s “stop trying because your judgment doesn’t matter here and I clearly don’t trust you with the decision of how to do this.”
Psychologists Edward Deci and Richard Ryan’s research on self-determination theory goes deeper still. People need three things to be engaged:
autonomy,
competence, and
relatedness.
Autonomy is the sense that you have agency in how you work. Competence is the sense that you can actually do the work well. Relatedness is the sense that the people you’re working with actually value you.
When a leader prevents autonomy by constantly checking in and redoing work, they’re not protecting anything. They’re dismantling the conditions under which people actually think. A person can have massive competence and still disengage if autonomy is gone. Remove the sense that your judgment matters, and everything else follows.
If you are planning summer 2027 travel, I have something worth your time. In July of 2027, I will be on an AmaWaterways river cruise sailing the Rhine from Amsterdam to Basel. Seven nights. Rhine Castles. Swiss Alps. Brodie, my wife and luxury travel designer at M. Markham Travel, has secured exclusive preferred rates on this specific sailing just for GSL readers and listeners. Come find me on the deck. Bring whatever you are working through. We will talk.
See the full itinerary and lock in your rate at mmarkhamtravel.com/GSL
Why Leaders Correct Instead of Translating Urgency
I realized this problem years ago while building up a team. I brought operational urgency from my vendor background into a company that was already deeply client-focused. But I was channeling that sense of urgency the wrong way. I checked in constantly on delegated work; I redid tasks when they weren’t meeting my standard, and the team perceived this as control rather than care.
What changed everything for me was what Kim Scott calls “radical candor”. I received candid feedback and was completely open, receptive, and grateful for what they said to me.
What I understood that day is simple: the team didn’t yet understand why urgency mattered. They didn’t see the connection between speed and relationships. They didn’t know that a delayed response to a client question, issue, or problem could be read by that client as indifference. And instead of spending my leadership energy on translation, I was spending it on correction.
I was preventing autonomy by refusing to trust the team I loved with the judgment of how to do the work I loved. And every time I redid something, I reinforced the message that their thinking wasn’t welcome here. The irony is that the urgency I cared so much about wasn’t actually coming through in my corrections. What came through was control.
There’s a massive difference. Urgency rooted in client care makes teams move faster because they understand what they’re moving toward. Urgency enforced through monitoring and rework slows teams down because they’re waiting for approval instead of thinking through the problem.
The Real Cost of the Delegation Lie to Managers
Think about the actual cost of the delegation lie over time. You have a manager who checks in constantly and redoes work. That manager is working nights and weekends because they’re doing their work and redoing everyone else’s. They’re exhausted. Their team is disengaged because nothing they do feels like it’s good enough. Turnover is high. Training costs are high. And the work product, which the manager is convinced requires their level of control to protect, actually suffers because it’s being filtered through exhaustion and surveillance.
Now imagine a different scenario. A manager sets clear boundaries about what matters most. Speed, accuracy, client relationship, whatever it is. Then the manager lets the team run. The manager does check-ins, but they’re about progress against the goal, not about approval of the method. The manager makes their expertise available, but the team is driving.
Over time, the team actually gets faster. They develop judgment about what matters because they’ve been trusted with it. They catch their own errors because they own the work. They call the manager when they hit a genuine constraint, not for permission. And the manager is freed to think about the next thing instead of redoing today’s work.
One scenario burns you out. The other scales you.
The Difference Between Guardrails and Micromanagement
Guardrails enable autonomy. They say “here’s the boundary. Here’s what I care about most. Within that, you decide.” Micromanagement prevents autonomy. It says “here’s exactly how you’re going to do this, and I’m going to watch.”
The guardrails conversation sounds like this: “I need this by Thursday because the client reviews on Friday. The format matters because it goes directly to the decision-maker. Beyond that, how you get there is your call. If you hit a wall, call me. Otherwise, I’ll see it when it’s done.”
The micromanagement version sounds like this: “I’ll handle the format. You handle the research. I’ll review it before you send it. Then I’ll probably rework it.”
One conversation delegates authority with constraints. The other delegates labor under surveillance. One says, “I trust your judgment about how to get here.” The other says “I don’t trust your judgment about anything.”
Guardrails also reveal trust. When a leader sets a boundary and then lets it be crossed without intervention, the team learns that the leader meant what they said. Micromanagement reveals the opposite. The team learns that the stated boundaries aren’t real. The real rule is “do what I would do.”
How to Run the "Silence Test" to Fix Micromanagement
For one week, delegate a task to someone on your team and make a deal with yourself: no check-ins unless asked directly. No redoing the work. No corrections unless something is actually off the rails.
Don’t just do this passively. Track it. Write down every time you have the urge to check in. Write down why. What was the trigger? What were you afraid would happen? Was it about the quality of the work or about your need to be in control?
At the end of that week, look at the list. Most leaders discover that the reason is rarely about protecting quality. It’s about protecting the feeling of being in control. It’s about the anxiety that comes from not knowing. It’s about the fear that if you’re not watching, something will fall apart and it will be your fault.
That’s the trap. And it’s worth seeing clearly.
The Eulogy Question: Building Accountability vs. Compliance
What version of yourself are you building right now? You might believe you are protecting quality, but the reality of leadership is captured in a single distinction: you either build people up or you keep them small. Those two outcomes are never the same.
Nobody’s eulogy praises a leader for redoing work because nobody else could do it right. The legacy that remains is whether you developed judgment in the people around you or simply extracted compliance.
The delegation lie is a defense mechanism protecting your need for control. Real protection looks entirely different. It means building a team that catches its own errors because they own the work. It means creating an environment where people call you for your deep expertise, not for your permission.
That is the credential worth protecting. Everything else is just work.
What to Listen to Next
The Silence Test in Action: Listen to Ep. 62: Deep Listening and True Silence
Explore how practicing silence and resisting the urge to jump in build critical judgment within your team.
Overcoming Management Anxiety: Listen to Ep. 45: Managing the Urge to Control
Learn how to track and manage your internal anxiety instead of passing it down to your team as micromanagement.
