Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Who Never Says No
Transcript
- Lucas: If we have helped you think through a career move or a leadership decision recently, I want to take thirty seconds to ask for your support. We run this network completely ad-free, which means our only revenue comes from listeners like you who chip in monthly through buy me a coffee dot com slash fexingo. It is literally what funds the research and production that keeps these episodes coming out every single day. Luna: Yeah, it really does make a difference in keeping the quality high without interrupting the flow with ads. So let us get into it. Lucas: We usually talk about managing the difficult employee—the one who argues, delays, or openly resists direction. But today I want to flip that script. I want to talk about the employee who never says no. The one who nods enthusiastically in every meeting, volunteers for every committee, and takes on every extra task you throw their way. On the surface, they look like the perfect team member. Underneath, they are quietly burning out, and you likely don't even realize it until it is too late. Luna: Right, because as a manager, it feels good to have someone who is so eager and cooperative. It validates your leadership style. Lucas: Exactly. And that is the trap. When an employee always says yes, it creates a false sense of security for you. You assume their workload is manageable because they are handling it all. But what happens is that they start dropping balls in areas you aren't watching, or they deliver mediocre work on critical projects because they simply do not have the bandwidth. I saw this happen with a senior analyst at a logistics firm last year. She said yes to leading a new reporting dashboard, helping with the annual audit, and mentoring two junior hires—all in the same quarter. She looked exhausted by November, but she never complained once. Luna: That sounds terrifying because she probably thought complaining would make her look unable to handle the pressure. Lucas: It is almost always rooted in anxiety or a lack of psychological safety. They believe that if they say no, they will be seen as lazy, uncommitted, or replaceable. So they overpromise and underdeliver, not out of malice, but out of fear. The problem for you as a manager is that you are now managing based on incomplete data. You think you have four hands available when you actually only have two. Luna: So how do you break that cycle without making them feel like you are punishing them for being helpful? Lucas: You have to change the narrative around what a good answer looks like. Most managers reward the immediate yes. You need to start rewarding the thoughtful no. Start your one-on-ones by asking about capacity, not just output. Ask them what they are worried about missing, rather than what they have accomplished. It shifts the conversation from performance review to resource planning. Luna: That makes sense because it forces them to articulate their constraints instead of just swallowing them. Lucas: Precisely. Let me give you a concrete example of how to phrase this. Instead of asking 'Can you take this on?', which invites a reflexive yes, try saying 'I am thinking about putting this initiative on your plate. Given your current projects, what would you need to drop or defer to make room for it?' This forces them to do the mental math of trade-offs. If they say they cannot drop anything, then you have a real conversation about prioritization. If they say yes again, you gently push back and ask why they feel they cannot say no. Luna: I love that because it puts the ball back in their court to manage their own bandwidth. Lucas: It does, and it also signals that you respect their time enough to expect them to protect it. But there is a deeper layer here. Some of these yes-people are actually hiding a lack of confidence. They think if they just do enough tasks, they will prove their worth. In that case, you have to reinforce the value of depth over breadth. Tell them explicitly that doing one thing exceptionally well is more valuable to the company than doing five things adequately. Luna: Do you find that this is more common in certain industries or roles? Like maybe creative fields versus operations? Lucas: It is pervasive, but it manifests differently. In sales, it might mean taking on too many small deals that distract from big ones. In engineering, it might mean trying to fix every bug ticket instead of focusing on the core architecture. I actually see it most often in individual contributors who are being groomed for management. They are terrified that if they aren't visible everywhere, they will be overlooked for promotion. So they spread themselves incredibly thin. Luna: That is such a counterintuitive strategy. Spreading yourself thin to get promoted? Lucas: It is, but it is very common. They confuse visibility with impact. As a manager, you have to show them that strategic focus is a leadership trait. When you deny them a request, frame it as coaching them toward that higher level. Say something like, 'I am not giving you this task because I want you to master the art of saying no to low-value work so you can focus on the high-leverage projects that matter for your next step.' Luna: That reframes the rejection as investment, which is brilliant. Lucas: It is, but you have to be consistent. If you tell them to prioritize but then still dump work on them when you are stressed, you lose all credibility. You have to model the behavior you want to see. When you ask for help, show them how you evaluate your own capacity. Say out loud, 'I have three priorities right now, and this new request doesn't fit. So I am going to delegate it or push it to next month.' Make your decision-making process transparent. Luna: Transparency is key because otherwise they just assume you have infinite capacity too. Lucas: Exactly. And another thing to watch for is the silent resentment that builds up. Even if they keep saying yes, their engagement metrics will drop. They will stop volunteering ideas, they will become less collaborative in meetings, and they might start calling in sick more often. These are the early warning signs that the yes-man facade is cracking. You need to catch that shift before they quit entirely. Luna: So it is really about proactive check-ins rather than waiting for the quarterly review. Lucas: Yes. And you can use a simple tool called the Capacity Heatmap. Once a month, sit down with each direct report and map their current projects against their energy levels. Use a simple red, yellow, green system. Green means they have room for more. Yellow means they are at capacity and any new task requires dropping something else. Red means they are overloaded and need immediate relief. It takes the emotion out of the conversation and makes it purely logistical. Luna: That is a great practical framework. It removes the ambiguity of whether they are busy or just bad at time management. Lucas: It does. And it gives you data to back up your decisions. If they are in the red zone, you can confidently say, 'I see you are at capacity here. I am not going to add anything new until we clear some of this backlog.' It protects them from themselves. But remember, you might face resistance. They might insist they can squeeze it in. That is when you have to hold the line. Gently remind them that their well-being is part of the job description. Luna: It feels like you are teaching them permission to rest, which is a luxury many professionals don't give themselves. Lucas: It is, and it is one of the most important gifts you can give them. Because eventually, the bill comes due. Either they burn out, or they leave, or they start dragging down the whole team with their stress. Managing the yes-person is really about managing the health of your entire unit. It requires you to be comfortable with a little bit of short-term friction to ensure long-term sustainability. Luna: I think a lot of managers avoid that friction because they just want harmony in the team. Lucas: Harmony is nice, but performance and sustainability are better. If everyone is saying yes, nobody is actually doing the hard work of prioritization. And prioritization is where the real value is created. So encourage healthy disagreement. Reward the person who says, 'I can do A or B, but not both unless we extend the deadline.' That is the kind of thinking that drives mature organizations. Luna: So basically, you want to create a culture where saying no is seen as professional competence. Lucas: Spot on. It signals that you understand your limits and respect the team's resources. It is the opposite of arrogance. Arrogance is thinking you can do everything. Competence is knowing what you can realistically achieve and sticking to it. If you can instill that mindset in your team, you will have fewer crises, higher quality work, and much happier employees. Luna: That is a powerful shift in perspective. It turns a potential conflict into a training opportunity. Lucas: Exactly. And it starts with you modeling that behavior every single day. So the next time someone asks you for something, pause. Check your heatmap. And if you are full, practice saying no with grace and clarity. Your team will notice, and they will thank you for it later. Luna: Well said. It is definitely a skill that takes practice, but the payoff for team health is huge.