Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Delegate Without Losing Control
Transcript
- Lucas: We need to talk about the difference between giving someone a task and giving them ownership. It sounds like the same thing when you are in the thick of it, but if you have ever watched a new manager struggle to let go of the wheel, you know they are fundamentally different. Luna: Right, because usually what happens is the manager gives the task but keeps all the context, so the employee is just executing blindly. Lucas: Exactly. And then the manager gets anxious because they don't see the intermediate steps, so they start checking in every hour. What starts as a simple delegation turns into a bottleneck where the manager ends up doing more work than the person they assigned it to. Luna: It is basically reverse outsourcing, isn't it? You hire someone to solve problems, then you create the problems by not solving them with them. Lucas: That is a sharp way to put it. The core issue is often that managers confuse clarity with control. They think if they explain every single detail, the result will be perfect. But in reality, they are just hoarding information that should belong to the team. Luna: So the listener might be thinking, well, I just need to explain it better next time. But is that really the solution? Lucas: No, because explaining it better just means you are spending more time teaching instead of letting them learn through doing. The shift has to be structural. We need to move from transactional delegation to contextual delegation. Luna: Contextual delegation. I like that term. How does that actually look in a Monday morning meeting? Lucas: Let us break it down. Transactional delegation is saying, 'Please finish this report by Friday.' Contextual delegation includes the why, the constraints, the stakeholders involved, and the definition of done. It is about transferring the mental model, not just the to-do item. Luna: Okay, but that sounds like a lot of upfront time. Managers are already stretched thin on October seventh, 2026, and everyone is juggling more responsibilities than ever. Lucas: I hear you, and it feels heavier initially. But think about the follow-up calls. If you spend twenty minutes setting the context properly, you might save two hours of back and forth emails later. It is an investment that pays off immediately. Luna: So it is less about working harder upfront and more about preventing the chaos downstream. Lucas: Precisely. And there is another layer here which is risk tolerance. New managers often feel that if something goes wrong, it reflects poorly on them. So they hover. But you cannot build a resilient team if you do not allow for small, correctible failures. Luna: That is the hard part though. Admitting that your team might make a mistake before you even let them try. Lucas: It is scary, but necessary. You have to define the boundaries of acceptable risk beforehand. Tell them exactly where the guardrails are. If they stay within those lines, they have total freedom on how to get there. Luna: So you are essentially creating a sandbox. As long as they play inside the fence, you don't care how they build the castle. Lucas: That is a great analogy. And it changes the dynamic from supervisor to coach. You are no longer watching their hands; you are looking at their strategy. That frees you up to handle higher-level problems while they develop their own judgment. Luna: But what if they do cross the line? What if they step outside those guardrails? Lucas: Then you have a learning moment, not a crisis. The key is to debrief without blame. Ask them why they made that choice. Did they misunderstand the context? Or did they have a better idea that conflicted with your assumption? Either way, you update the framework. Luna: So the framework evolves. It is not a one-time instruction manual that sits on a shelf. Lucas: It is a living document, both literally and figuratively. The best managers I know treat their delegation style as a hypothesis. They test it, see how the team responds, and adjust based on the data. Luna: I love that. It takes the emotion out of it. It becomes a system optimization rather than a personal test of authority. Lucas: Exactly. And it builds trust. When your team sees that you gave them the full picture and trusted them to execute, they feel valued. When you hover, they feel policed. Luna: There is a huge morale difference there. People want to feel like professionals, not cogs. Lucas: They absolutely do. And ironically, giving them that professional space makes them more accountable. They own the outcome because they owned the process. Luna: So the lesson is: give context, set boundaries, and then step back. Lucas: Step back and let them breathe. But keep an eye on the horizon, not the ground beneath their feet. Luna: That is a nice image. Looking at the horizon while they drive. Lucas: Before we go deeper into the mechanics of that debrief, I want to pause for a second. We have been talking about how much time and energy goes into managing people effectively. Luna: Yeah, and keeping these conversations going requires support too. Lucas: If we have helped you navigate a career move or a management challenge recently, consider supporting the show directly. Your contribution helps keep Fexingo ad-free and allows us to keep digging into these topics. Luna: You can find us at buy me a coffee dot com slash fexingo. It really makes a difference for the team behind the mic. Lucas: Thanks for listening. Now, let us get back to that debrief process, because that is where most managers stumble. Luna: Right, the debrief. Because if you don't do it right, you might undo all that trust you just built. Lucas: Spot on. A bad debrief feels like an interrogation. A good debrief feels like a calibration. The goal is to align your mental models for next time. Luna: So you ask open-ended questions. Like, 'What did you think was the biggest hurdle?' rather than 'Why didn't you do X?' Lucas: Yes. You want to understand their decision-making tree. Did they have enough information? Were there external blockers? Or did they simply prioritize differently than you expected? Luna: And sometimes the answer is that they prioritized differently because you didn't clarify the priority. Lucas: Which brings us back to the original point. Context includes priorities. If you don't tell them what matters most, they will guess. And guessing is expensive. Luna: So clarity is kindness. It saves everyone from the anxiety of guessing. Lucas: It is the kindest thing you can do. It removes the ambiguity that causes stress. When people know exactly what success looks like, they can focus on achieving it. Luna: I think that is the takeaway for anyone feeling overwhelmed by their team's output. Slow down the handoff. Lucas: Invest in the setup. The rest tends to fall into place. Luna: Agreed. Less hovering, more helping. Lucas: Let us see if we can apply that to our own workload tomorrow. Who needs a clearer context today? Luna: I bet we both have at least one person in mind. Let us figure out how to set them free.