Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage an Employee Who Always Volunteers for Extra Work
Transcript
- Lucas: So let me paint a picture. You've got this person on your team who every time there's a new project, a stretch assignment, a cross-functional task force — their hand is up before you've even finished the sentence. Luna: Right, the classic 'yes person.' At first it feels like a blessing. Lucas: Exactly. You think, wow, I've got someone who actually wants more responsibility. But then you start noticing cracks. The quality of their core work starts slipping. They seem distracted in one-on-ones. Maybe they're the first one in and the last one out. And then, six months later, they resign. Luna: And you're blindsided because they were the one asking for more. That's the paradox we're digging into today. Lucas: Right. There's a real difference between someone who has genuine capacity and ambition and someone who is using overwork as a coping mechanism — or just can't say no. And as a manager, your job is to tell the difference before the system breaks. Luna: I want to ground this in a real example. Can we talk about the case you mentioned from a mid-size SaaS company? Lucas: Yeah, I had a conversation with a VP of Engineering at a company called CloudLoyal — about 400 employees, B2B analytics. She told me about a senior engineer named Priya who was constantly raising her hand. She led the migration to a new database, volunteered for an on-call rotation, joined the DEI council, and mentored three junior devs. On paper, a star. Luna: And then? Lucas: After about eight months, Priya's pull request review rate dropped by 40 percent. She started missing sprint commitments. The VP pulled her aside and Priya broke down. She said she felt like she couldn't say no because she thought that's what high performers do. She was terrified of being seen as not committed. Luna: That's heartbreaking. And it's so common. There's actually a Microsoft Workplace Analytics study that looked at this — employees who take on more than five active projects at once see a 22 percent drop in quality. Lucas: Twenty-two percent is massive. And the irony is, the person volunteering for everything is often the one you can least afford to lose. So the intervention has to be proactive, not reactive. Luna: So how do you spot the difference between healthy ambition and overcommitment? What's your framework? Lucas: I call it the three-bucket test. When an employee volunteers for something new, you ask yourself three questions. First, is this aligned with their core role and growth path? Second, do they have the bandwidth after you look at their actual calendar — not their stated hours? Third, is the underlying motivation curiosity and energy, or fear and guilt? Luna: The third one is the hardest to assess, especially in a fifteen-minute chat. How do you get at that? Lucas: You slow down the conversation. When someone says 'I'd love to take that on,' you don't just say 'great.' You say 'tell me what excites you about this' or 'what would you deprioritize to make room?' Their answer tells you everything. If they say 'everything is equally important,' that's a red flag. Luna: So you're training them to think about trade-offs explicitly. That's smart. Lucas: Exactly. And once you've done that assessment, you have two paths. If it's a genuine high-potential case, you protect their time ruthlessly — maybe you even strip something else off their plate. If it's a fear-driven case, you coach them on boundaries and give them permission to say no. Luna: Which brings us to the donation segment — and I promise this connects. Because we're talking about protecting people from overcommitment, and honestly, this podcast is a labor of love that we protect by keeping it ad-free. A couple of dollars a month from listeners is genuinely what keeps these episodes coming. Lucas: Yeah, if you've gotten something out of Manager Mondays — maybe one of these frameworks helped you with a real situation — consider throwing a few bucks our way at buy me a coffee dot com slash fexingo. It's small, it's sincere, and it lets us keep doing this without sponsors. Luna: And we mean it when we say every contribution adds up. So thank you. Now back to Priya. Lucas: So the VP of Engineering at CloudLoyal sat down with Priya and they did a version of the three-bucket test together. They listed every commitment Priya had, and they categorized them into 'must keep,' 'could delegate,' and 'could stop entirely.' Luna: I love that she did it collaboratively, not top-down. Lucas: Exactly. Priya ended up dropping the DEI council — not because she didn't care, but because she realized she was doing it out of guilt. She delegated one of the junior mentorship relationships to another senior engineer. And they set a hard rule: no more than two non-core projects at any time. Luna: And did her performance recover? Lucas: Within two sprints, her pull request quality was back up. She actually started leaving at 5:30. And six months later, she told the VP that the conversation had been the most impactful of her career. She felt seen, not controlled. Luna: That's the goal. So for managers listening, what's the one thing you can do this week? Lucas: Pick one person on your team who says yes to everything. In your next one-on-one, ask them: 'If you could only do one thing really well this quarter, what would it be?' Then listen. And if they name something that isn't their biggest deliverable, you have your opening. Luna: And if they say 'everything'? Lucas: Then you have your work cut out for you. But at least you know where to start.