Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says Yes to Everything
Transcript
- Lucas: So, let's talk about the employee who says yes to everything. You know the one — they volunteer for every project, never push back on a request, and their calendar looks like a game of Tetris that's about to lose. Luna: Oh, I know that person. I've been that person. And I've managed that person too. It's deceptively dangerous because it looks like enthusiasm at first. Lucas: Exactly right. A 2025 study from the Society for Human Resource Management found that employees who overcommit — defined as regularly taking on more tasks than they can realistically complete — are 40 percent more likely to experience burnout within six months. And here's the kicker: managers often reward this behavior with praise and more responsibility, which accelerates the collapse. Luna: Forty percent — that's huge. And you're right, we tend to see it as a positive. 'So committed, so eager.' But it's often a coping mechanism or a fear response. Lucas: Before we dig into the tactics, a quick note — and this is sincere. We keep this show ad-free by design. No sponsors, no mid-roll interruptions. If you've found episodes like this useful in your own management practice, the simplest way to support that choice is buy me a coffee dot com slash fexingo. It's a small gesture that keeps us independent and focused on what's useful. Now, back to the yes-machine. Luna: Yeah, it really does help. And it's nice to know the show exists just because listeners want it to. So, where do we start with the person who can't say no? Lucas: Let me give you a specific case. I was talking to a VP of engineering at a mid-size SaaS company — about 300 employees. She had a senior data analyst, stellar performer, who said yes to leading three cross-functional projects simultaneously: a pricing model overhaul, a customer churn analysis, and a new reporting dashboard. He missed every single deadline across all three. Luna: Classic. And I bet the VP felt blindsided because he'd been so agreeable. Lucas: Exactly. She said she'd never had a complaint from him. He'd always say 'I can take that on' or 'Sure, no problem.' The problem was, he was saying yes because he feared that saying no would make him look less capable. He didn't have a framework for assessing his own capacity, and neither did she. Luna: So whose fault is that? I mean, the employee needs to learn to say no, but the manager is the one stacking the plates. Lucas: It's shared. But as a manager, you have more leverage and more responsibility to create the conditions. The employee can't solve this alone. So let me offer three concrete tactics. First: the traffic light capacity signal. Luna: I like the name. What is it? Lucas: You work with the employee to define a simple visual indicator of their current workload. Green means 'I have bandwidth for one more task.' Yellow means 'I can take something on only if something else gets deprioritized.' Red means 'I am at full capacity — any new request will break something.' The employee updates this weekly, and you agree to respect it. It turns the 'yes or no' decision into a data point. Luna: So it depersonalizes the refusal. The employee isn't saying 'no' — they're saying 'I'm red this week.' That's smart. Lucas: Exactly. And it forces the manager to be explicit about priorities. If you're asking someone who's red to take on more, you're making a trade-off, and you need to name it. Second tactic: the pre-commitment pause. Luna: This one sounds like it's about slowing down the reflex. Lucas: Right. Before the employee says yes to any request — especially in the moment, in a meeting or on Slack — they commit to a pause. They say 'Let me check my current workload and get back to you within the hour.' That hour gives them time to assess whether they actually have the capacity. It also signals to the requester that the answer isn't automatic. Luna: That's hard for people who are people-pleasers. They feel like they're letting someone down just by not answering immediately. Lucas: It is hard. But you can normalize it as a team practice. If everyone does it, it becomes culture, not defiance. And the third tactic is maybe the most counterintuitive: the weekly 'no' practice. Luna: You're going to ask them to practice saying no? Lucas: In a safe, low-stakes way. At your one-on-one, you give them a hypothetical request — something that's clearly outside their scope — and ask them to say no to you. You role-play it. 'Hey, can you take over the monthly ops report for another team?' And they have to articulate why they're saying no. It builds the muscle in a situation where there's no real consequence. Luna: That's actually brilliant. Because the fear is usually about the unknown reaction. If they practice with you and see that you don't get angry, they learn that saying no is safe. Lucas: Exactly. Over time, they internalize that 'no' is a legitimate response, not a failure. Now, I want to address something you hinted at earlier: is this really a manager problem or a cultural problem? Luna: Yeah, because if the whole org rewards heroics — people who pull all-nighters and take on everything — then one manager's efforts might feel like swimming upstream. Lucas: It's true. A toxic culture of overwork can undermine individual good practice. But here's my take: as a manager, you have a sphere of influence. You can't fix the entire org, but you can protect your team from the worst of it. And if you do it consistently, your team's performance and retention will stand out. That becomes a proof case that gets noticed. Luna: Okay, but what about the employee who says yes to everything because they genuinely don't know their own limits? They're not people-pleasing out of fear — they're just naive or overconfident. Lucas: That's a different flavor, but the tactics still apply. The traffic light system gives them an objective measure. The pre-commitment pause forces them to assess. And the 'no' practice still helps them develop judgment. The underlying skill is the same: realistic self-assessment. Luna: So it's less about personality and more about building a skill. That's a helpful reframe. Lucas: Exactly. And as the manager, you're the coach. You're not there to scold them for overcommitting — you're there to give them the tools to make better decisions. One last thing: watch for the quiet signs that the yes-machine is breaking down. Missed deadlines, lower quality work, withdrawal from team conversations, or a sudden drop in energy. Luna: Those are the signals that the 'yes' strategy has hit its limit. By then, it's often too late to prevent burnout — you're in recovery mode. Lucas: Right. So the goal is to intervene before that point. Have the conversation early. Use the tactics. And remind them that their value isn't measured by how much they take on — it's measured by what they actually deliver. Luna: I think that's a note a lot of managers need to hear too. We can be complicit in this cycle without realizing it. Lucas: Absolutely. So next time you see someone on your team who always says yes, ask yourself: are they really that eager, or are they drowning quietly? And then give them permission to pause. Luna: Good note to end on. Thanks, Lucas. Lucas: Thanks, Luna. See everyone next time.