Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / Asking for a Raise When You Are the Only One Who Can Do the Job
Transcript
- Lucas: So Luna, let's talk about a listener question we get all the time, but I don't think we've ever done a full episode on it: what do you do when you are literally the only person who can do your job? Luna: Oh, that's a good one. And I bet a lot of people listening right now are thinking, 'Yeah, that's me.' Lucas: Right, and it feels like you should have all the leverage in the world. I mean, if you're the only one who knows how the system works, or the only one with that certification, or the only one who's been there long enough to remember why things are the way they are, shouldn't your boss just hand you a raise? But the reality is often the opposite. Luna: What do you mean by 'the opposite'? Like, you get passed over because they can't afford to lose you? Lucas: Exactly. There's this classic trap called the 'indispensable employee' problem. You become so critical to day-to-day operations that your manager is terrified to promote you, because then they'd have to replace you. So you get stuck in the same role, with the same pay, doing the same work, because you're 'too valuable' to move. Luna: That sounds maddening. So what's the play? How do you actually turn that into a raise without threatening to quit? Lucas: Well, first, let's be clear: being the only one who can do your job is not inherently a bad thing. It's a position of strength, but only if you manage it correctly. The key is to make your value visible and quantifiable, and to give your manager a path forward that doesn't feel like a cliff. Luna: Okay, so what does that look like in practice? Can you give us a concrete example? Lucas: Sure. I remember reading about a mid-sized software firm, about two hundred employees, and they had a single data engineer. Let's call her Priya. She built and maintained their entire data pipeline. If she took a day off, every report in the company was late. If she left, they'd have to hire a consultant at three times her salary for months. She knew she had leverage, but she also knew that just walking in and saying 'I'm the only one who can do this, give me a raise' would probably backfire. Luna: Right, because that sounds like a threat, even if you don't mean it that way. Lucas: Exactly. So Priya did something smart. She spent a month documenting her work: every task, every system she touched, every report that depended on her. She estimated that if she were to leave, it would take at least six months to hire a replacement and get them up to speed, and she put a dollar figure on that. Then she went to her manager and said, 'I want to talk about my compensation, and here's what I've been doing, and here's what it would cost to replace me.' Luna: So she made it about the business, not about her ego. That's smart. But did it work? Lucas: It did, but not in the way you might expect. Her manager listened, nodded, and then said, 'You're right, we can't afford to lose you. But we don't have budget for a raise right now.' So Priya didn't get the twenty percent bump she was hoping for. Instead, she got something arguably more valuable: a commitment to train a backup. Luna: Interesting. So she traded the raise for a successor? That doesn't sound like a win at first. Lucas: But it was, because it changed the conversation. Once there was a backup in training, she wasn't indispensable anymore. And that gave her the leverage to go back and say, 'Now that I've made myself replaceable, my value is even clearer. I've enabled the company to reduce risk, and I'd like a raise that reflects my contribution, not just my irreplaceability.' And she ended up getting a fifteen percent raise and a promotion to a team lead role, because she was no longer the bottleneck. Luna: Hmm, so the strategy is to make yourself less indispensable, not more. That's counterintuitive, but I can see the logic. If you're the only one who can do the job, you're stuck. If you're the one who can do the job and train others, you're valuable and mobile. Lucas: Exactly. And this is a lesson we've seen play out across industries, from solo IT admins to the only accountant at a small firm. The first step is always to do the documentation, to quantify your impact. The second step is to propose a solution that makes you less of a single point of failure. And then you can have a real conversation about compensation. Luna: It sounds simple, but I'm sure it's not. What are some of the common mistakes people make in this situation? Lucas: The biggest mistake is going in without data. If you just say 'I'm the only one who can do this,' your manager hears 'I'm going to quit.' And that puts them in a defensive position. They might panic and give you a small raise just to keep you, but it won't be the raise you deserve, and it can breed resentment. Luna: Right, you don't want to be the employee who's known for making threats. Lucas: No, you want to be the employee who's known for solving problems. And the other mistake is not considering the long-term. If you're the only one who can do your job, you might be indispensable today, but what happens when the company decides to outsource that function, or when a new technology makes your skill obsolete? You want to be indispensable because of your judgment and your ability to grow, not just because you're the only one who knows the password to the server. Luna: So we're not just talking about a raise, we're talking about career resilience. That's a bigger picture. Lucas: Yeah, and that's the kind of advice we like to give on this show. Which is a good segue to a quick honest thing, if you'll indulge me for a second. Luna: Sure, go ahead. Lucas: Look, we make a lot of these episodes, and they're free for everyone, no ads, no paywall. And that's only possible because a small group of listeners chips in a few dollars a month through buy me a coffee dot com slash fexingo. It's not a big ask, it's just if this show has helped you think through a career move or a tricky conversation, and you want to keep it going, that's the way to do it. We're grateful for every single one of you who does. Luna: Yeah, it really does make a difference, and it lets us keep doing deep dives like this one. Lucas: So back to Priya. The takeaway isn't just 'document your work and train a backup.' It's also about recognizing when you have a genuine leverage point, and then using it strategically. Because if you're the only one who can do your job, you have a responsibility to your own career to either get paid for that risk or to eliminate that risk and get paid for the value you create. Luna: And I think there's another angle here. What if you're in a situation where you're the only one, but you actually want to stay in that role? You enjoy the depth, you don't want to manage a team. Is there a way to get a raise without necessarily becoming a manager? Lucas: Great point. There are technical tracks and individual contributor tracks at many companies now. So you can propose that. You can say, 'I want to continue doing this work, but I'd like to be recognized at a senior level, maybe with a title change and a pay adjustment.' That way you're not asking for a promotion out of the role, you're asking for the role to be valued properly. Luna: That makes sense. And I've also seen people use the 'market data' angle. If you're the only one with a particular skill set, you can pull salary surveys for that niche and show that the market rate is higher than what you're being paid. Lucas: Absolutely. And that's a good way to make the conversation about external reality, not just your own perception. So to bring it all together: if you're the only one who can do your job, you have three options. One, you can make yourself less indispensable by training others, and then negotiate from a position of mobility. Two, you can stay in the role and ask for the role to be reclassified and paid at market rate. Or three, you can leverage your unique position to negotiate a retention bonus or a project-based premium, especially if there's a critical deadline or a knowledge transfer period. Luna: That third option is interesting. Can you give an example of that? Lucas: Sure. Imagine you're the only person who knows how to migrate the company's legacy system to a new platform, and they've got a deadline to do it by the end of the year. You could say, 'Look, I'm happy to lead this migration, but it's a significant extra responsibility, and I'd like a bonus for successful completion.' That's a way to get a lump sum without changing your base salary. Luna: So there are creative options beyond just 'give me a raise.' It's about understanding what the company needs from you and how they value that in the moment. Lucas: Exactly. And the underlying principle is this: being the only one who can do your job is not a guarantee of a raise. It's a condition that you need to manage. The question is, are you going to be the one who's anxious about being irreplaceable, or are you going to be the one who's confident in your value and willing to have the conversation? Luna: And I think that's the real takeaway. It's not about the raise itself, it's about taking control of your career narrative. Lucas: Yeah, and if you're listening and you're in that position right now, I'd love to know what you decide to do. We're always interested in hearing how these strategies play out in the real world. But for now, that's our take on the 'only one who can do it' conundrum. Thanks for being here, and we'll catch you in the next episode.