Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Can Delegate Their First Big Project
Transcript
- Lucas: So let me start with a story. A friend of mine became a manager at a mid-sized SaaS company about four months ago. Smart guy, great individual contributor. His first big test came when his director asked him to deliver a custom analytics report for a top-tier client. Deadline was tight, stakes were high. Luna: And he did what most new managers do — he stayed up until 2 a.m. building it himself, right? Lucas: Exactly. He wrote the SQL queries, designed the dashboard, checked the numbers three times. And the report was great. But his own team? They didn't touch it. He burned out, they felt sidelined, and the client got a great report but zero knowledge transfer. Luna: So the problem wasn't the quality. It was that he skipped the entire delegation step. Lucas: Right. And this is the single hardest muscle for new managers to build. You've been rewarded your whole career for doing things well yourself. Now suddenly your job is to get things done through other people, and the quality feels like it's out of your hands. Luna: So what did he do differently the next time? Because there's always a next time. Lucas: He used what I call the 'three-layer brief.' It's a way to hand off a project so the person executing it has enough context to make good decisions without you hovering. Layer one is the strategic context — why this client matters, what the business goal is, why the report is structured the way it is. Luna: So not just 'here's what to do,' but 'here's why we're doing it.' Lucas: Exactly. Layer two is the success criteria. Not a checklist, but three to five indicators that tell you the deliverable is solid. For that report, it was things like 'data sources are documented,' 'all numbers reconcile with the source system,' and 'the narrative explains the key takeaway in under two sentences.' Luna: That gives the person boundaries without prescribing every step. Lucas: Right. And layer three is the support plan. Not 'call me if you need anything,' which is useless, but specific checkpoints: 'After you've pulled the raw data, let's do a 15-minute sync before you start building the visuals.' That way you catch errors early without micromanaging. Luna: I love that. Because the fear is always 'what if they do it wrong and I have to redo it anyway?' Lucas: That fear is legitimate. And honestly, sometimes the work will come back wrong. But if you've set up the checkpoints, you catch it before it's a disaster. My friend delegated the second report to a junior analyst named Priya. She took the brief, asked a few clarifying questions, and delivered it two days early. It wasn't perfect — he had to tweak one chart — but she learned, and he didn't burn the midnight oil. Luna: So what about the manager's own mindset? Because I think a lot of new managers secretly believe that if they delegate, they're admitting they can't do it themselves. Lucas: That's a huge psychological barrier. There's this identity shift from 'I am the person who solves problems' to 'I am the person who grows other people.' It sounds corny, but it's real. And the data backs it up — managers who delegate effectively have teams with higher retention and faster development. Luna: Yeah, I've seen that. There's a classic study from Google's Project Oxygen that found coaching and empowering others was one of the top traits of high-performing managers. Lucas: Exactly. So the practical takeaway is: start small. Don't delegate your biggest client report first. Delegate a smaller piece — maybe the data pull, or the first draft of a memo. Build trust on both sides. Luna: And be explicit about what you're delegating. I've seen managers say 'can you take care of this?' and the person interprets it as 'do the whole thing,' then the manager is surprised when it's not what they wanted. Lucas: Right. Clarity is kindness. The three-layer brief forces that clarity. And if you're the one being delegated to, you can ask for it. Say 'can you walk me through the context, the success criteria, and when you'd like to check in?' Luna: That's a power move for a junior person too. Lucas: Absolutely. Alright, I think we've covered the core framework. But there's one more thing I want to touch on: what to do when the work comes back wrong. Luna: Yes, that's the fear that stops people from delegating in the first place. Lucas: So you get the deliverable and it's not up to standard. First reaction: don't fix it yourself. That's the trap. Instead, sit down with the person and say 'let's look at this together against the success criteria.' Let them see where it falls short. Luna: So it becomes a coaching moment, not a rescue mission. Lucas: Exactly. You ask 'what do you think is missing?' Often they already know. If they don't, you guide them to see it. Then you ask 'what would you do differently?' Let them own the fix. It takes longer in the moment, but the next time they'll be faster. Luna: That's the real ROI of delegation — not just getting the work done, but building a team that can do it without you. Lucas: And that's the whole point of being a manager. If you're still the best person on your team at the actual work, you're not managing — you're just a senior individual contributor with a title. Luna: Harsh, but fair. Lucas: It's a reframe I wish someone had given me on day one. Delegation isn't about losing control. It's about multiplying your impact. Luna: And if this episode helped you reframe your own approach to delegation, that's exactly why we make this show. If you've found value in these conversations, you can support the show at buy me a coffee dot com slash fexingo. It's a small way to keep this ad-free and focused on real, practical advice. Lucas: Yeah, listener support is what lets us spend time on episodes like this — digging into one concrete challenge instead of just surface-level tips. So if you've gotten something out of it, that link is buy me a coffee dot com slash fexingo. Luna: Alright, back to delegation. One last thought: have you ever seen a manager delegate something that was clearly too important to delegate? Lucas: Oh, absolutely. There's a flip side. You don't want to delegate something that is genuinely too complex or too high-stakes for a junior person. But that's where the three-layer brief helps — you can delegate pieces. Let them own the data pull while you handle the client-facing narrative. Luna: So delegation is a spectrum, not a binary. Lucas: Right. And as a new manager, your job is to gradually expand the scope of what you delegate as your team's capabilities grow. Start with small, low-risk tasks. Then medium. Then bigger. By month six, you should be delegating real projects. Luna: And if you're the team member being delegated to, how do you make the most of it? Lucas: Ask for the three layers. Show that you understand the context. Deliver early and ask for feedback. That builds trust fast. And when you inevitably make a mistake, own it, learn from it, and communicate proactively. Luna: Great advice. So to recap: use the three-layer brief, start small, and treat mistakes as coaching opportunities. Lucas: And if you're still the one doing all the work, you're not delegating. You're just overwhelmed. Luna: That's the episode. Thanks, Lucas. Lucas: Thanks, Luna. See you next time.