Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Why Good Managers Fail At Delegation
Transcript
- Lucas: We often hear that the hardest part of becoming a manager is letting go of being the best player on the field. But I have noticed something more subtle happening lately. It is not just about letting go; it is about how we define what gets handed over. Most new managers treat delegation like a checklist of tasks to offload. Luna: Right. They send an email with five bullet points and expect someone else to figure out the rest. That is not delegation, that is dumping. Lucas: Exactly. And it usually comes from a place of good intention. You are busy, the deadline is looming, and you know exactly how to do the work. So you give instructions instead of giving context. The problem is that the recipient feels managed, not trusted. Let us talk about the specific moment where this goes wrong. It is rarely in the planning phase. Luna: It is always in the execution phase when things get slightly messy. The manager jumps in to fix it because fixing is faster than teaching. Lucas: That speed trap is real. Think about the last time you had to redo someone else’s work. Did you feel frustrated? Probably. Now imagine you are the one who did the work. You spent three days on a report, your manager tweaks two paragraphs, and sends it out with their name on it. What happens next week? Luna: You stop trying. Why risk criticism if the boss is going to change it anyway? That is the quiet demotivation most teams suffer from. Lucas: So here is the core argument for today. Delegation is not about efficiency. It is about development. If you delegate to save time today, you create a bottleneck for tomorrow. You need to delegate to build capacity for next year. This requires a shift from delegating activities to delegating outcomes. An activity is a task. An outcome is a result. Luna: Can you give us a concrete example of that difference? Because on paper they sound similar until you actually try to write them down. Lucas: Sure. Activity-based delegation sounds like this: please draft the quarterly sales presentation using our standard template. Outcome-based delegation sounds like this: I need you to secure approval from the regional director by Friday. Figure out which slides matter most to convince them. Which one makes you nervous? Luna: The second one. Because now I have to make judgment calls. I don't know if my judgment is good enough yet. Lucas: That nervousness is the point. Growth lives there. When you assign an activity, you remove the judgment call. You turn the employee into a robot executing steps. When you assign an outcome, you force them to think like a manager. You are asking them to prioritize, to assess risk, and to communicate trade-offs. That is the skill gap most new leaders ignore. Luna: But doesn't that require more upfront time from the manager? You have to explain the goal, the constraints, and the success criteria. Isn't that slower than just telling them what to do? Lucas: It is slower in the hour of setup. But it is faster in the week of review. If you assign an activity, you will spend hours correcting formatting, tone, and structure. If you assign an outcome, you only intervene if they are heading toward the wrong finish line. You check in on milestones, not minutiae. The friction moves upstream. Luna: I see. So you are trading immediate control for long-term leverage. But what about the fear that they will mess up the client relationship? Lucas: That is the competence curse again. You assume they will fail because you would have done it differently. But different does not mean wrong. The trick is to set guardrails, not rails. Guardrails tell you where the edge of the road is. Rails tell you exactly which lane to stay in. New managers love rails because they feel safe. Luna: And rails kill creativity. Or at least they kill the sense of ownership. If I am just staying in my lane, I am not responsible for getting us there. Lucas: Precisely. Responsibility sticks to ownership. If you want someone to care about the result, you have to let them own the path. This means allowing them to choose the tools, the sequence, and sometimes even the people they collaborate with. It sounds chaotic if you are used to tight control. Luna: It does sound scary. Especially if you have a reputation for being precise. Your team might wait for you to tell them how to be precise. Lucas: That is a hard habit to break. You have to explicitly give permission for variation. Say this out loud: I do not care how you get there as long as we hit the target by Wednesday. Then shut up. Do not hover. Do not ask for daily updates unless you agreed on them beforehand. Hovering signals distrust. Luna: Hovering is basically micromanagement in slow motion. It tells the employee that you are watching, not supporting. Lucas: Right. Support looks like removing obstacles. Micromanagement looks like adding checkpoints. There is a massive difference. When you move to outcome-based delegation, your role shifts from executor to blocker-remover. You are no longer doing the work. You are clearing the path so they can do the work. Luna: So the metric changes too. You stop measuring effort or hours logged. You start measuring impact and velocity. Lucas: Exactly. And this creates a feedback loop. When the employee succeeds, they feel proud. When they fail, they learn. If you micromanage, they never learn because you made the decisions for them. You rob them of the chance to understand why a certain approach failed. That is dangerous for their career growth. Luna: It also protects you. If you keep doing everything, you become indispensable in the worst way. If you leave, the whole department collapses. That is not a promotion strategy, Lucas. That is a hostage situation. Lucas: A very apt description. The best managers are the ones who make themselves replaceable in the day-to-day so they can focus on strategy. You cannot scale if you are the bottleneck for every minor decision. Scaling requires systems, and delegation is the human system. Luna: What about the employees who actually prefer clear instructions? Some people hate ambiguity. They want to be told exactly what to do. Lucas: That is a fair point. Not everyone wants to lead. Some people want to specialize. For those folks, activity-based delegation is fine. Let them be excellent specialists. But for anyone you want to grow into a leader, you must push them toward outcomes. You have to coach them through the ambiguity. Ask questions instead of giving answers. Luna: Coaching through ambiguity. I like that phrase. It implies you are walking alongside them, not standing behind them with a whip. Lucas: Walking alongside. Yes. And that brings me to the final piece of the puzzle. The debrief. After the outcome is delivered, you sit down and review it. Not to critique, but to calibrate. What worked? What felt hard? What would you do differently next time? This turns a single task into a learning module. Luna: That debrief is where the magic happens. It reinforces the behavior you want to see. It shows you value their thinking process, not just the output. Lucas: It builds psychological safety. They realize that mistakes are data, not disasters. Once they trust that, they take bigger risks. They propose better ideas. The team starts moving faster because they are not waiting for your stamp of approval on every little thing. Luna: It transforms the culture from compliance to contribution. People stop asking what they should do and start asking what needs to be done. Lucas: That is the ultimate goal. A self-managing team. Of course, it takes time to get there. You will make mistakes along the way. You might pick the wrong person for an outcome-based assignment. That happens. Just be transparent about it. Admit you misjudged the fit and adjust. Luna: Admitting misjudgment builds more trust than pretending you never err. It shows humility and adaptability. Lucas: Absolutely. Leadership is not about being right all the time. It is about being honest about where you are going and who you need to help you get there. Delegation is how you find out who can help. Luna: So, to wrap this up for our listeners who are starting their Monday morning with a heavy inbox: stop looking at your list of tasks. Start looking at your list of opportunities to teach. Lucas: Pick one item on your plate today. The one you are dreading doing. Instead of doing it, write down the desired outcome. Define the guardrails. Hand it off. And then resist the urge to touch it for forty-eight hours. See what happens. Luna: If it breaks, you fix the system. If it works, you gain back your time. Either way, you win. Lucas: Before we sign off, I want to mention something important. We put a lot of effort into these conversations because we believe management is a craft worth studying. It is not innate. It is learned. And keeping this network independent means relying on listeners like you. If this conversation helped you shift your perspective today, consider supporting us directly. Luna: It keeps the show ad-free and allows us to dig deeper into topics like this one. You can support the work at buy me a coffee dot com slash fexingo. Any amount helps us keep the lights on and the mugs full. Lucas: Thank you for listening. Now, go delegate something. You might be surprised by what your team can do when you finally step back.