Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Who Always Says I Need a Raise
Transcript
- Lucas: So, Luna, you've been a manager for a few years now. What's the one conversation that still makes your stomach drop? Luna: Honestly, it's not the firing or the PIP. It's the 'I need a raise' conversation. Especially when it comes out of nowhere. Lucas: Right. And I think that's because as managers, we're never really trained for it. We know how to set goals, how to give feedback, but when an employee asks for more money, we freeze. We worry about budget, about fairness across the team, about whether they'll leave if we say no. Luna: And the worst part is when they come with an ultimatum: 'I have another offer' or 'I've been here three years, I deserve a bump.' What do you do with that? Lucas: Exactly. And that's what we're digging into today — the anatomy of the raise request and how to handle it without wrecking the relationship or the budget. Let me set the scene with a composite example that I see all the time. Say you've got a marketing coordinator named Maya. She's been at a mid-sized tech firm for about 18 months. She's solid — hits deadlines, runs the social calendar, pitches in when the team's swamped. But she hasn't really gone above and beyond. One Tuesday, she pops into your office and says, 'I need a raise. I've been doing good work, and I'm not making market rate.' Luna: And your first instinct is to get defensive, right? Or to promise you'll look into it and then never follow up. Lucas: Exactly. But the key is to turn that moment into a structured conversation. So the first rule is: never say yes or no on the spot. The moment you give a quick yes, you've created an anchoring problem — you've set the baseline for any future negotiation, and you haven't done the homework to see if it's fair. And a quick no just escalates the situation. So the first move is to buy time, but not in a stalling way. You say something like, 'I appreciate you bringing this up. I want to give it a fair look, so let's set aside time this week to talk through your contributions and what the market data says. Can you grab a 30-minute slot for Thursday?' Luna: That buys you time to actually prepare. And I like that you're framing it as a conversation, not a verdict. Lucas: Right. And the preparation is crucial. You need to pull together three things: the employee's actual performance over the past year, the market data for their role and experience level, and your own budget constraints — what's the max you can go, if anything. Now, for Maya, you'd pull her last two reviews, look at her project outcomes, check if she's taken on any extra responsibilities. And you'd look at salary band data for a marketing coordinator in your city. There are tools like Glassdoor, Payscale, or even your HR department's internal bands. Luna: But here's the tricky part — market data is never a single number. It's a range, and the employee might be looking at a different site than you. So how do you handle the 'I'm underpaid' argument? Lucas: That's where you have to be transparent about the data you're using. In the meeting, you don't just say 'here's what we can do.' You say, 'I pulled data from three sources, and the median for your role in this market is fifty-eight thousand, with a range from fifty-two to sixty-five thousand. Your current salary is fifty-five thousand, so you're within the range, but on the lower end. Based on your performance, I think we can make a case for moving you to fifty-eight.' That's a concrete, data-backed offer that acknowledges their point without giving in to an arbitrary number. Luna: And you're not just saying 'no' — you're showing your work. That makes the employee feel heard, even if they don't get exactly what they asked for. Lucas: Exactly. But the bigger issue is that a lot of managers miss the underlying need. Sometimes the raise request is really about recognition, or feeling undervalued, or wanting more responsibility. So you need to ask open-ended questions in that meeting. 'What's driving this for you? Is it the money, or is there something else?' You might find out they're feeling stretched thin or they want a title change. And you can address those needs even if the budget is zero. Luna: That's a good point. I remember a manager once told me that an employee asked for a raise, and it turned out they just wanted a better job title to put on their resume. They were planning to leave in six months. A title change cost nothing and kept them engaged for another year. Lucas: And that's the kind of creative problem-solving that separates good managers from great ones. But let's get back to the standard raise conversation. The second rule is: separate pay from performance. That sounds counterintuitive — they're linked, right? But the mistake is to let the raise conversation become a performance review. If the employee's performance hasn't warranted a raise, you need to say that clearly: 'I appreciate your initiative, and I want to recognize your effort, but the data doesn't support a raise right now. Here's what I need to see in the next six months to revisit this.' And you lay out specific, measurable goals. That's actually a growth opportunity, not a rejection. Luna: So you're turning the 'no' into a development plan. But what if the employee is performing well and you just don't have the budget? That's a tough spot. Lucas: That's the third rule: don't promise what you can't deliver. If the budget is frozen, you say, 'I hear you, and I think you're making a fair case. But I have constraints I can't ignore. What I can do is advocate for you at the next review cycle. In the meantime, here's what I can do: I can offer you a one-time bonus, or I can adjust your responsibilities so you're building skills that will justify a larger increase later.' And you set a specific date to revisit — not 'someday,' but 'let's check back in October.' Luna: And you put that in writing? Because I've seen too many managers say 'we'll revisit' and then nothing happens. Lucas: Absolutely. Follow up with an email summarizing the conversation, the agreed next steps, and the timeline. That protects both of you. And it shows the employee you take them seriously. Luna: Now, what about the employee who comes with a competing offer? That's a whole different beast. Lucas: That's the fourth rule: never get into a bidding war. If someone says, 'I have an offer from another company,' your first response should be curiosity, not panic. Say, 'I'm glad you told me. What's the offer, and what's driving your decision?' Sometimes it's not just money — it's commute, or role scope, or culture. If it is just money, you have a choice: match it or don't. But if you match it, you need to be prepared to do it again in a year. Better to use that moment to discuss total compensation — bonus, stock, benefits, flexibility — and see if you can structure a package that meets their needs without breaking your bands. Luna: And if you can't match it, you have to be honest and wish them well. But you can also ask for a 'counter-counter' — like, 'If we can't match the salary, would you stay for a different title or a development opportunity?' Lucas: Exactly. And that brings me to the fifth rule, which I think is the most important: make compensation a continuous conversation, not a once-a-year event. The best managers have a short conversation with each team member at the start of every quarter. It's not a formal review, just a check-in: 'How's your workload? Are you learning? What could make this role better for you?' That way, you have a sense of what's on their mind long before they feel the need to come to you with a raise demand. Luna: That makes so much sense. If you're having regular conversations, the raise request doesn't feel like a bomb. It's just a natural evolution. Lucas: Right. And it also helps you avoid the 'tipping point' scenario, where an employee feels so undervalued that they've already mentally checked out. By then, even a big raise might not retain them. Luna: That's such a key insight, and it's something we've talked about on this show before — how proactive communication prevents so many reactive crises. And that's actually part of why we love making this podcast. It's our way of helping managers and professionals have better conversations, and we're able to keep the show free and focused because of listener support. If you've found value in what we do, you can back us at buy me a coffee dot com slash fexingo. It's a simple way to keep the coffee brewing and the episodes coming. And every bit helps us stay independent and ad-free. Lucas: And we really do appreciate that. Now, let's get back to the mechanics. So we've covered not making snap decisions, separating pay from performance, handling budget constraints, and avoiding bidding wars. The last piece is how to handle the aftermath — especially if you've said no. Luna: The aftermath, yeah. Because even if you've handled it well, the employee might still feel disappointed. How do you keep them engaged? Lucas: You have to monitor their engagement in the weeks after. Schedule a follow-up meeting, say in a month. Ask them how they're feeling about their work, and if they've seen any progress on the goals you set together. If they're still fixated on the money, you might need to have a more honest conversation about their long-term fit. But if they've bought into the development plan, make sure you're genuinely investing in them — give them stretch assignments, mentorship, exposure to senior leaders. That's how you build loyalty that's not just salary-based. Luna: And what if you said no, and then they go quiet? That's the classic silent resignation. They're still doing the work, but they've checked out. Lucas: That's a red flag. You need to address it directly. Say, 'I've noticed you've been more quiet lately. I want to make sure we're on the same page. Are you still committed to the goals we set?' If they say they're fine, but the behavior doesn't change, you might need to have a deeper conversation about their career aspirations and whether this role can meet them. Luna: That's a tough conversation, but better than pretending everything's okay and then losing them six months later. Lucas: Absolutely. And there's one more piece I want to touch on, and that's the system level. As a manager, you should also be looking at compensation equity across your team. If you've given raises to some but not others, make sure you can justify it. That's where having clear performance metrics and a compensation philosophy helps. You don't want to be in a position where you're making ad-hoc decisions based on who asks first. Luna: So the takeaway is that the raise conversation is really a leadership conversation. It's about building trust, not just about the money. Lucas: Exactly. And the best managers treat every raise request as an opportunity to strengthen the relationship, not as a threat. So next time Maya walks into your office, you can take a breath, pull out your data, and have a conversation that leaves both of you feeling respected. Luna: And if you're a listener who's about to have that conversation, good luck. You've got this. Lucas: And if you want more tools like this, we're here every week. Thanks for joining us.