Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / The Art of Delegating as a First-Time Manager
Transcript
- Lucas: There is a stat from a Harvard Business Review study that has stuck with me for years. They surveyed over a thousand new managers, and the single biggest skill gap they reported — more than giving feedback, more than running meetings — was delegation. Roughly 60 percent said they struggled to let go of work they should have handed off. Luna: That tracks. I remember my first six months as a manager, I was still coding on weekends because I thought no one else could do it right. It was exhausting and frankly dumb in hindsight. Lucas: Right, and the irony is that you were hired to manage, not to do the individual contributor work. But the instinct to hold on is so strong. The thing is, delegation is not just about freeing up your calendar. It's about building capability in your team. If you never hand off the meaty stuff, your people never learn. Luna: So how do you break that cycle? Because the logical part of your brain knows you should delegate, but when you're staring at a deadline, the emotional part just takes over and does it yourself. Lucas: One framework I like comes from a book called 'The 70 Percent Rule' by a former Navy SEAL officer. The idea is simple: if someone on your team can do a task 70 percent as well as you can, delegate it. Not 90 percent, not 100 percent — 70 percent. You accept some imperfection in exchange for their growth and your time. Luna: Seventy percent feels low. I think I would have struggled with that. What if the task is client-facing or high-stakes? Lucas: That's a fair point. The rule applies more to internal, developmental tasks. For high-stakes stuff, you'd still oversee closely. But the principle is: don't wait until someone is perfect. They won't get perfect without practice. So you hand off the task, you set clear expectations, you check in at milestones, and you let them run. Luna: Okay, so let's get practical. Walk me through a specific case. How does a first-time manager actually start delegating when they've got a backlog and a team that's already stretched? Lucas: Let's use a real example. I worked with a manager named Melissa at a mid-size SaaS company. She was promoted from senior engineer to engineering manager of a five-person team. For the first six months, she was still writing code, fixing bugs, and attending every stand-up. She was burning out, and her team felt like she didn't trust them. Luna: Classic. What did she change? Lucas: She started with what I call a delegation audit. She listed every task she did in a week — all 40-plus hours of it. Then she marked each task: 'only I can do', 'someone else could learn to do', 'someone else already can do'. She found that about 70 percent of her tasks fell into the second or third bucket. Luna: That must have been a wake-up call. Seven out of ten hours were tasks she didn't need to own. Lucas: Exactly. Then she prioritized which tasks to delegate first. She didn't try to hand off everything at once. She picked three tasks that were well-defined, low-risk, and matched the skills of specific team members. For each task, she scheduled a 20-minute delegation conversation. Luna: What did that conversation look like? Because I've seen delegation fail when the manager just says 'here, you do this' without context. Lucas: Right, that's dumping, not delegating. Melissa used a simple script: 'I want you to own X. Here's why it matters. Here's what done looks like. Here are the resources available. And I want you to come to me if you hit a roadblock, but otherwise, I trust you to figure it out.' She also set a check-in at 25 percent completion so she could course-correct early. Luna: That check-in at 25 percent is smart. It's early enough to fix problems but not so early that you're micromanaging. I've made the mistake of checking in too late — like at 90 percent — and then having to redo the whole thing. Lucas: Oh, that hurts. And it's demoralizing for the team member too. They put in all that work and then you're like 'start over'. So the 25 percent checkpoint is a safety net for both of you. Luna: What about delegating upward? I've never quite figured that out. Like, how do you hand a task to your own boss without it feeling awkward? Lucas: That's a great question and a real skill. The key is framing it as a strategic ask. You don't say 'I can't do this, you do it'. You say 'I think this task would benefit from your perspective or authority. Would you be willing to take the lead on this one while I focus on X?' Make it about leveraging their strengths, not dumping your work. Luna: I like that. I tried something similar once: I asked my VP to review a cross-functional proposal because he had relationships with the other department heads. He actually appreciated being looped in early. Lucas: And that's the thing — good leaders want to be used effectively. If you delegate upward wisely, it shows you're thinking strategically about how to use everyone's time, including theirs. Luna: Let's talk about delegation failures. Because not every handoff goes smoothly. What happens when the person drops the ball? Lucas: First, you resist the urge to say 'I should have done it myself'. That thought is the enemy of delegation. Instead, you do a blame-free postmortem. You ask: what was unclear about the task? Did they have the right resources? Was the deadline realistic? Often the failure is in the setup, not the person. Luna: I once delegated a data analysis task to a junior analyst, but I didn't explain which metrics mattered most. She came back with a 40-page report full of every possible metric. It was my fault for not giving her a filter. Lucas: Exactly. So when something goes wrong, you look at the system first. And then you have a coaching conversation: 'Here's what happened, here's what we learned, here's how we'll adjust next time.' That builds resilience and trust. Luna: So delegation is really about teaching and trusting. It's not a transactional exchange. It's a developmental process. Lucas: That's exactly right. And it's also a multiplier. If you can free up 10 hours a week by delegating well, that's 500 hours a year you can spend on higher-impact work — strategy, coaching, your own development. That's huge. Luna: Speaking of impact, I want to mention something that makes shows like this possible. We keep these episodes free and ad-free, and that's because listeners like you chip in a couple of dollars a month on Buy Me a Coffee. It genuinely covers the hosting costs and keeps us going. If you've gotten value from these management conversations, you can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, and it's a small thing that makes a big difference. We appreciate everyone who's supported the show. Now back to delegation — we talked about delegating tasks, but what about delegating authority? That's the next level. Luna: What's the difference? Delegating a task is giving someone a to-do. Delegating authority is giving them decision rights. That's scarier for most managers. Lucas: Much scarier. But it's also more powerful. When you delegate authority, you're saying 'I trust you to make decisions in this area without checking with me first.' You set boundaries — like a budget limit or a scope — and then you let go. That's how you develop real leaders on your team. Luna: I remember a time my manager delegated authority to me for vendor selection. She said 'you can choose any vendor under $10,000 without my sign-off.' That trust made me work twice as hard to prove I deserved it. Lucas: That's the effect. When people feel trusted, they step up. And if they make a mistake, you treat it as a learning opportunity. The cost of a small mistake is usually far less than the cost of having a manager bottleneck every decision. Luna: So for a first-time manager listening, what's the one thing they should do tomorrow to start delegating better? Lucas: Do the delegation audit I mentioned. Spend 30 minutes looking at your calendar and to-do list. Identify three tasks that someone else could do at 70 percent quality. Then schedule a 20-minute handoff conversation for each one this week. That's it. Start small. Luna: And if the team is already overwhelmed? You can't just pile on more work. Lucas: Good point. You might need to help them reprioritize. Ask your team: what's on your plate that could be dropped, delayed, or done differently? Make room for the delegated tasks. It's not about adding — it's about swapping. Luna: Swapping, not dumping. I love that. Let's crystallize a few takeaways. First, use the 70 percent rule. Second, do a delegation audit. Third, frame delegation as development, not offloading. Fourth, delegate authority, not just tasks. And fifth, when things go wrong, look at the system first. Lucas: That's a solid summary. I'd add one more: celebrate when delegation works. When a team member completes a task well, acknowledge it publicly. That reinforces the behavior and shows the whole team that you trust them with meaningful work. Luna: And that builds a culture where people want to take on more. It's a virtuous cycle. Alright, I think we've given our listeners a practical playbook. Next week, we're going to talk about something that came up in the comments — how to manage a team member who is technically brilliant but terrible at communication. Lucas: That's a classic challenge. See you then.