Latest / Executive Careers with Fexingo: VP, C-Suite, and Senior Leadership Career Strategy / How Senior Leaders Delegate Without Losing Control
Transcript
- Lucas: So I want to start with a story about a chief operating officer at a major consumer goods company, and I'm not going to name them, but their name is, let's call him Dave. Dave was recently promoted to the COO role, and he was handed a massive integration project, two business units being merged. He knew he couldn't do it alone, so he delegated the whole thing to his two top lieutenants. And then he did what a lot of new senior leaders do, he checked in every single week, asked for detailed slide decks, and basically inserted himself into every major decision. Luna: So he delegated but he didn't actually let go. Lucas: Exactly. And the result was a mess. The team felt second-guessed, decisions stalled, and Dave was spending more time on that project than he ever did before. It was the classic delegation paradox, he thought he was delegating but he was just creating more work for himself. And three months in, the project was behind schedule and Dave was about to pull the plug on the whole delegation idea. Luna: So what did he do? Did he go back to doing everything himself? Lucas: He almost did. But he brought in a coach who told him to stop delegating the tasks and start delegating the outcomes. That's the phrase, and it sounds simple, but it's actually a really specific framework. The coach had him map out what he called decision rights and information rights for every part of the project. Who had the right to make a decision, and who had the right to be informed about it. And once Dave wrote that down, everything changed. Luna: Decision rights and information rights. That's a nice clean way to think about it. So he had to decide which decisions he was actually going to make himself. Lucas: Right. And he found that he only really needed to make about a dozen strategic calls over the course of the project, like the overall timeline, the budget range, and the integration of the two corporate cultures. Everything else, his lieutenants could handle. But he also realized that he wanted information on every major milestone, not because he was going to second-guess them, but because he needed to be an effective spokesperson to the board and the rest of the company. Luna: So the information rights were about him being informed, not about him controlling the decisions. Lucas: Exactly. And that's the crux of it. When Dave started to separate those two, the follow-up meetings dropped by about forty percent. He went from weekly hour-long status meetings to a fifteen-minute check-in every two weeks, and a one-page written update. His team suddenly had the space to actually work, and Dave had the time to focus on the board, the CEO, and the next big thing. It transformed his effectiveness. Luna: That forty percent number is striking. And it makes sense, because when you're micromanaging, every meeting is a review of something you've already seen. But when you delegate the outcome, you're only meeting about the exceptions or the strategic calls. Lucas: And that's the framework I want to dig into today, because I think a lot of senior leaders, especially when they're new in a role, default to Dave's first model. They delegate the work but they keep the control. And it's actually a real problem in the current market. In August 2026, companies are asking executives to do more with less, and scaling yourself is the only way to make it work. Luna: So let's talk about that first principle, delegating outcomes instead of tasks. What does that look like in practice? Lucas: Well, think about the difference between saying, 'I want you to create a slide deck on the market analysis' versus 'I want you to determine whether we should enter the Latin American market by the end of the quarter, and here's what I'll need to make that call.' The first is a task, the second is an outcome. And when you delegate the outcome, you're giving the person the latitude to figure out the how, and you're also clarifying what you need from them to make a decision. Luna: That makes sense. But isn't there a risk that you're not staying close enough to the details? I mean, as a leader, you're ultimately accountable for the result. Lucas: That's the classic tension, and it's why decision rights are so important. You're accountable, so you get to decide which decisions you're going to own. But for everything else, you're delegating the authority along with the responsibility. The key is that you're not delegating and walking away, you're delegating with a clear structure for how you'll stay informed and when you'll step in. Luna: So how do you actually map out those decision rights? Do you have a practical method? Lucas: Yeah. One approach is the RAPID model, which stands for Recommend, Agree, Perform, Input, and Decide. You go through every major decision in the project and you assign who's doing each role. For example, in Dave's case, the decision on the new organizational structure, his head of HR would recommend, Dave would agree, the integration lead would perform the implementation, and the regional heads would input. And Dave would be the one to decide, but only after he'd heard from everyone. Luna: That's a concrete tool. And it forces you to be explicit about who has the final say. It probably also surfaces when you're the bottleneck without realizing it. Lucas: Exactly. A lot of leaders think they're agile because they're in every meeting, but they're actually the bottleneck. By mapping decision rights, you can see it clearly. And you can also see where you're giving input when you should be letting someone else decide. There's a discipline to only weigh in on things that actually need your voice. Luna: And that forty percent drop in meetings, that's just the time savings. What about the quality of the work? Did Dave see improvement there? Lucas: He did. And that's the part that really sold him. When his team stopped waiting for his approval, they started bringing him better options. They knew he was going to ask for the trade-offs, so they prepared two or three viable paths and made a recommendation. The quality of the thinking went up because they owned the outcome. And that's what you want, you want people who are thinking like owners, not like order-takers. Luna: That's the real payoff. You're not just freeing up your calendar, you're developing your team. And in the long run, that's what earns you the bigger role. Lucas: Right. And I think that's the deeper point, delegation isn't just about getting work off your plate, it's about growing your leadership capacity. And I'm not just talking about the team, I'm talking about you. When you delegate outcomes, you free yourself to focus on the strategic work that only you can do. And that's how you scale your impact. Luna: Let's talk about the flip side, though, because I feel like there's a common pitfall where leaders delegate the outcome but then they hover anyway. How do you avoid that? Lucas: That's where the information rights come back in. You have to be clear about how often you want to be updated and in what format. And you have to stick to that. If you've agreed to a weekly one-page update, then you don't call on Wednesday for a detailed walkthrough. You trust the process. Luna: But what if you get the update and you see something that's off? Are you supposed to stay silent? Lucas: No, you have to intervene. But you do it in a way that respects the decision rights you set up. You don't swoop in and take over. You ask a question that helps them see the issue themselves. Something like, 'I notice you're planning to launch in the second quarter, what's the risk if we slip to the third?' That way, you're guiding, not directing. Luna: So it's a coaching mindset. That's a real shift for a lot of executives who are used to being the one with all the answers. Lucas: It is. And honestly, that's the hardest part. In my own experience, I've seen leaders who are brilliant operators, they're the best at doing the work, but they struggle to let go because they're so good at it. But the higher you go, the less you're paid to do the work and the more you're paid to make sure the work gets done well by others. And that's a different skill set. Luna: So how does a leader prepare for that mindset shift? I mean, you've got to convince yourself that letting go is actually the better strategy. Lucas: One practical exercise is to pick one project where you're currently deep in the weeds, and ask yourself, 'What would have to be true for me to hand this off?' And then create a plan for that. What information would I need to feel confident? What milestones would I want to see? Who would I need to develop? And then hand it off with that structure in place. It's a low-risk way to start building the muscle. Luna: And it probably helps to start with something small, not the biggest project of the year. Lucas: Exactly. You don't want to test your new delegation skills on the highest-stakes thing you have. But once you see that the team can handle it, and that the work actually gets better, you gain the confidence to do it more and more. Luna: And that confidence, that's the thing. Because I think for a lot of leaders, the fear is that if the project fails, it's on them. So they feel like they have to keep their hands in it. But the truth is, if you've set the structure up right, you're still accountable, you're just not doing the work. And that's what leadership is. Lucas: Yeah. And I think that's the real unlocked door. When you can trust your team and yourself to handle the ambiguity, that's when you move from being a manager to being a leader. And that's the level where you get to have a real impact on the business, not just on your own to-do list. Luna: So if Dave were here, what's the one thing you'd tell him to do differently from day one? Lucas: I'd tell him to spend the first week mapping out decision rights and information rights before he even thinks about assigning tasks. Because once he did that, everything else clicked into place. And I'd tell him to communicate that map to his team, so they all knew who was responsible for what and when he was going to step in. That clarity is worth a hundred status meetings. Luna: And I'd add, make it visible. Put that map somewhere everyone can see it, like on a shared drive or a wiki. That way, there's no ambiguity, and people can self-manage around it. Lucas: That's a great point. And you know, it's funny, we talk about delegation as a time management tool, but it's really a communication tool. It's about setting clear expectations, and that's something I think we could all get better at. Luna: And I think it's also a trust tool. When you delegate with clear decision rights, you're telling your team, 'I trust you to make these calls, and I'm here for the big ones.' That's a powerful message. Lucas: It really is. And it's something that becomes more important as you move up, because the higher you go, the more you're dealing with complexity that you can't possibly know all the details of. You have to rely on your team, and the stronger your delegation structure, the more you can scale your leadership. Luna: And that's probably why it's such a sought-after skill in the current market. Companies are looking for leaders who can multiply themselves, not just do the work themselves. Lucas: Yeah, and I think that's worth a coffee. I mean, honestly, if today's episode helped you think about delegation in a new way, that's the link, buy me a coffee dot com slash fexingo. It's a small way to keep this podcast ad-free, and we appreciate it. Luna: And it really does help. So, if you're finding value in these conversations, that's the place to go. Lucas: Alright, so let's get back to the practical stuff. One of the things I love about the decision rights map is that it's not just for big projects, you can use it for any recurring decision you're involved in. For example, I've seen leaders use it for hiring decisions, budget approvals, even for how they run their executive team meetings. Luna: So the framework is universal. It's just about being intentional about who decides what and who knows what. Lucas: Exactly. And the more you do it, the more it becomes a habit. And then you start to see opportunities to delegate that you never saw before. And that's when the real transformation happens. Luna: I'm curious, have you seen any leader take this too far? Like, delegate so much that they become disconnected? Lucas: That's a real risk. If you delegate everything, including the things you should be doing, you become irrelevant. The key is to strike that balance. You delegate the operational, but you hold on to the strategic relationships and the vision. You stay informed through your information rights, but you don't get in the weeds. It's a delicate dance, but when you get it right, it's a beautiful thing. Luna: And that's what we all aspire to, right? To be the leader who can step back and let the team shine, while still being the one who guides the ship. Lucas: Absolutely. And I think that's a good place to leave it today. I hope this gives you a new lens on delegation. And remember, it's not about doing less, it's about doing more of what matters.