Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Saying No to a Star Employee Without Losing Them
Transcript
- Lucas: So, Luna, I was talking to a friend who runs a product team at a mid-sized tech company, and she had this moment with her strongest engineer. The guy who ships twice as fast as anyone else, who's basically carrying two projects on his back. And he walks into her office on a Monday morning and asks for a four-day workweek. Same pay, but he wants every Friday off. Luna: Oof. And I'm guessing she couldn't just say yes? Lucas: Right. The company policy is five days, and she doesn't have the authority to carve out an exception. So she's sitting there, looking at her best employee, and she has to tell him no. And she said to me, 'I've given him every raise, every bonus, every piece of interesting work. And the one time I have to say no, I feel like I'm going to lose him.' Luna: That is the classic manager's dilemma. You train up this great person, you give them everything, and then the one time you can't deliver, you're terrified they'll walk. Lucas: Exactly. And that fear is real. The Society for Human Resource Management ran a study earlier this year that found nearly sixty percent of employees would consider leaving a job if they felt their manager didn't support their career goals. So the stakes are high. But the thing is, saying no to a star employee doesn't have to be a relationship-ending event. There's a way to do it that actually strengthens your bond. Luna: Okay, I need to hear this. Because every piece of advice I've ever seen is about how to say yes — how to retain people by giving them what they want. Nobody talks about the no. Lucas: Well, that's the gap we're going to fill today. And the first thing to understand is the difference between a 'no, but' and a 'no, because.' Luna: Okay, I'm writing this down. 'No, but' versus 'no, because' — go. Lucas: So 'no, but' is what most of us do. My friend's first instinct was to say, 'I can't give you Fridays off, but I can give you a bonus at the end of the year.' And that's a classic mistake. When you attach a counteroffer to a no, it sounds like you're buying your way out of the conversation. It doesn't address the real motivation behind the request. Luna: Right, because the employee didn't just want money. They wanted a different way of working. Lucas: Exactly. So the 'no, because' approach starts with the reason. You say, 'Here's why I can't do this, and here's what that reason tells me about what you value.' So for my friend, it would sound like, 'I appreciate that you're asking for Fridays off. I know it's about getting more focused time for deep work, and I want to help you with that. But our policy is five days, and I can't make an exception without going through a formal process that could take months and could still be rejected. So I'll be honest with you — the answer is no for now, but let's figure out what we can do within the constraints.' Luna: Hmm. So you're not just shutting it down. You're acknowledging the why and leaving the door open for a different solution. Lucas: That's the key. The 'because' part is critical because it shows you've thought it through. It's not a lazy no. And it also gives the employee a sense of transparency — they can see the reasoning, and that builds trust, even if they don't like the answer. Luna: And you mentioned a formal process. So what if the employee says, 'Fine, let's go through the formal process'? Lucas: Good question. And that's where you have to be honest about whether it's a policy you could actually change or not. If it's a hard company-wide rule, you say, 'The policy isn't something I can override, and I want to be upfront with you about that so I'm not leading you on.' If it's something you could potentially support, then you say, 'Here's what I can do: I can take this to my manager, but I want to be realistic about the odds.' Luna: So you set expectations. And if you do go to bat for them, and it still doesn't work out, you haven't lost credibility because you were honest from the start. Lucas: Exactly. And that's the thing — your credibility is on the line. If you say 'maybe' when you mean 'no,' you're setting yourself up for a worse conversation down the road. Luna: So let's talk about the other scenario: the employee who asks for a promotion that isn't available. Or a title change that would put them above their peers. How is that different? Lucas: That's a different beast. Because a title change isn't just about the individual — it's about the team structure, the org chart, and pay bands. So the 'no' needs to come with a clear explanation of the hierarchy and what would have to happen for that title to be available. Luna: So it's not just 'I can't give you this' — it's 'here's the path to getting it, and here's what's realistically in the way.' Lucas: Right. And that's where you can turn a no into a development plan. You say, 'I can't give you the director title right now, because we don't have an open slot. But here are the three things you need to do over the next year to be ready when one opens up.' And if you're honest — if you really believe they have a shot — this becomes a motivating conversation, not a disappointing one. Luna: So you're giving them a roadmap instead of a dead end. That's the difference between a no that kills motivation and a no that actually fuels it. Lucas: Exactly. And that's the goal: you want to preserve the relationship and the employee's sense of forward momentum. But there's a bigger issue lurking here, and it's the one that trips up a lot of managers — the fear of losing the person outright. Luna: Right, because you can do everything right, and they still might leave. So how do you handle that? Lucas: You have to be okay with the possibility. And that's hard, especially when it's your star player. But if you're constantly making decisions based on 'what if this person quits,' you're not leading — you're hostage-taking. Actually, I read a really interesting piece in the Harvard Business Review about this exact problem. The author called it 'the tyranny of the high performer.' And the point was that when you let one person's potential departure dictate your decisions, you end up making bad calls for the whole team. Luna: So you're saying the manager's role is to serve the team, not just the star. Lucas: Exactly. And that's why the 'no' conversation is so important. It's not just about this one request — it's about setting a precedent for the whole team. If you cave to a star employee just because they're a star, everyone else will see it. And then what happens when someone else asks for Fridays off, and you have to say no because you already gave your best engineer an exception? You've created a fairness problem. Luna: That's a really good point. And it's something that a lot of managers don't think about in the heat of the moment. You're so worried about losing the star that you forget about the other nine people on the team. Lucas: Right. And that's why I love this framework. It forces you to slow down and think about the consequences. So let's say you've done all that — you've given the 'no, because,' you've offered an alternative, you've set expectations. What do you do if the employee still pushes back? Luna: Oh, I think that's the part that makes people lose sleep. The pushback. Lucas: So the first thing is, you don't cave just because they push back. But you also don't shut them down. You say, 'I hear you. I know this is important to you. Let me be clear about my constraints, and let's work together to see if there's any wiggle room.' And then you actually listen. Maybe there's a compromise you haven't thought of. But if there isn't, you hold the line. The worst thing you can do is say 'maybe' and then never follow up. Luna: So it's about being firm but not rigid. And if they still can't accept it, then maybe it's time for them to move on. Which is a hard truth. Lucas: It is. But sometimes the best thing you can do for a high performer is to let them go somewhere that can give them what you can't. And if you've been honest and supportive, they'll remember you as a good manager. They might even come back someday. Luna: That's a really mature way to look at it. And I think it's actually the core of what we're talking about — managing people isn't about keeping them forever, it's about helping them grow, even if that growth takes them away from you. Lucas: Exactly. And that's a philosophy that will serve you well throughout your career. So let's wrap up with a few practical takeaways. First, always lead with the reason for the no. Second, offer a path forward, even if it's just a conversation about what they're looking for. And third, be willing to lose a star rather than compromise your integrity or your team's culture. Luna: And if you can do all that, you might just keep them anyway. Because people stay when they feel respected, even when the answer is no. Lucas: I think that's the perfect note to end on. So until next Monday, keep having those tough conversations — they're the ones that make you a better manager.