Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says That's Not My Goal
Transcript
- Lucas: You're in a one-on-one with a senior developer. You ask her to lead a cross-team documentation initiative — something critical for the next release. And she says, 'That's not really aligned with my personal career goals.' Luna: That's a tough one. It's not 'not my job' — it's 'not my goal.' That feels harder to push back on because it's wrapped in the language of development. Lucas: Exactly. And it's becoming more common. A lot of companies now ask employees to set annual goals — sometimes called 'personal development plans' or 'career growth plans.' And some employees use those written goals as a shield. They say, 'Look, I wrote down that I want to become a principal engineer. Spending time on documentation doesn't get me there.' Luna: So how do you respond? Because on one hand, you don't want to dismiss their ambition. On the other, you need the work done. Lucas: And that's the tension. A quick honest thing — a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that support is what keeps this show ad-free and lets us do deep dives on exactly these kinds of scenarios. So thank you to those who have. Luna: It really does make a difference. And it keeps us from having to run ads in the middle of a conversation about goal alignment. Lucas: Right. So back to that developer. The key is to take the goal seriously — but then connect the assignment to it. Documentation isn't just busywork. It's an opportunity to demonstrate technical leadership across teams, to influence how other engineers work, to set standards. That is principal-engineer behavior. Luna: So you're reframing the task as a stepping stone, not a detour. Lucas: Exactly. I call it the three-step framework. Step one: Validate the goal. Say, 'I appreciate that you're focused on becoming a principal engineer. That's a great ambition.' Step two: Connect the task. 'Leading this documentation effort will require you to influence peers without authority, to set technical standards, to review and approve contributions — those are exactly the competencies we look for in principal engineers.' Step three: Renegotiate if needed. If they still push back, you open the door: 'If you truly believe this doesn't serve your goal, let's talk about what would. But the documentation needs to be done. So we need to find a path forward.' Luna: I've seen that third step work really well. I had a junior marketer once who said a data analysis project wasn't aligned with her goal of becoming a brand manager. And I said, 'What would a brand manager do with customer data?' And she paused and said, 'Okay, I see your point.' Lucas: That's a great example. And sometimes the honest answer is that the goal itself needs updating. I had a senior engineer who wanted to be a principal, but after a few conversations, it became clear he actually wanted to be a staff engineer — more hands-on, less cross-team influence. Once we clarified that, the documentation project actually felt like a burden, not a opportunity. So we reassigned it. Luna: So the framework also surfaces misalignment between the employee's stated goal and what they actually want day-to-day. Lucas: Exactly. Sometimes 'that's not my goal' is a signal that the employee doesn't fully understand what their goal requires. Other times it's a polite way of saying 'I don't want to do this task.' And you have to treat those differently. If it's genuine misunderstanding, you educate. If it's resistance, you hold the line. But you can't just accept it at face value. Luna: What about the manager who doesn't have a clear picture of the employee's goals? Should goals be set in advance for this to work? Lucas: Ideally, yes. But in practice, a lot of teams don't have formal goal-setting. So when an employee says 'that's not my goal,' the first question is: 'What is your goal?' If they can't articulate it, then they're just using the phrase as a deflection. And you can call that out gently. 'Help me understand what your goal is, so I can see how this assignment fits or doesn't.' Luna: That forces the employee to be specific. I've seen cases where the employee's goal was 'become a better leader' — which is so vague that almost any assignment can be connected to it. Lucas: Right. And that's actually a problem. Vague goals are hard to work with. If someone says 'I want to grow as a leader,' you need to pin down what that means operationally. Does it mean managing people? Influencing without authority? Speaking at conferences? Each of those would connect to different assignments. Luna: So part of the manager's job is to help the employee set more concrete goals to begin with. Lucas: Yes. And that's a preventive step. But even with well-defined goals, you'll get this pushback. And I think the hardest version is when the employee is right — the task really doesn't serve their goal. In that case, you have two options: either you acknowledge that and reassign the task, or you explain why the task is still necessary for the team even if it doesn't advance their personal goal. And then you need to decide: is this a one-time ask, or is the role itself misaligned? Luna: That's a bigger conversation. If every task you assign them is 'not my goal,' then maybe they're in the wrong role. Lucas: Exactly. And that's a separate conversation — but it's a valid one. The worst outcome is when the manager just accepts the deflection and the employee never does the task, and the resentment builds on both sides. So the framework gives you a structured way to address it in the moment and then escalate if needed. Luna: What about the employee who uses goals to avoid any stretch assignment that's outside their comfort zone? Lucas: That's a common pattern. The goal becomes a comfort blanket. And as a manager, you have to distinguish between a genuine career path and a desire to stay in a narrow lane. I had a developer once who said his goal was to be 'the best backend engineer in the company.' That's a laudable goal, but it also let him refuse any frontend or full-stack work. I had to point out that being the best backend engineer meant understanding the full system context, which required some exposure to frontend. He wasn't convinced, so I ended up assigning a mentor who was a principal engineer and could make the case more credibly. Luna: So you used a peer to bridge the gap. Lucas: Yes. Sometimes the manager's voice isn't the most persuasive. A respected senior engineer saying 'this is how I got to where I am' can carry more weight. And that's another tool in the toolkit. Luna: I want to come back to the renegotiation step. What does that look like in practice? You said 'if you truly believe this doesn't serve your goal, let's talk about what would.' Then what? Lucas: Then you have a problem-solving conversation. Maybe they propose an alternative task that does serve their goal. If that alternative is equally valuable to the team, great — you swap. If it's less valuable, you negotiate. 'I can't give you that instead, but I can give you this smaller version, or I can schedule it for next quarter.' The point is to keep the conversation constructive and not let it become a standoff. Luna: And if they don't propose anything? Lucas: Then you're back to the original ask. 'I appreciate you thinking about it, but the documentation still needs to be done. I need you to lead it. Let's talk about how we can make it work for you.' That shifts from 'why' to 'how.' And that's usually more productive. Luna: I think one thing that makes this pattern so tricky is that it sounds reasonable. 'I'm just focusing on my goals.' Who can argue with that? Lucas: Exactly. It's cloaked in self-improvement. But as a manager, you have to remember that the employee's goals aren't the only thing that matters. The team's goals matter too. And the company's goals. It's a balance. The employee who always says 'that's not my goal' is effectively saying 'my goals come first, always.' And that's not sustainable for a team. Luna: So what's the one thing you'd want a first-time manager to take away from this episode? Lucas: Don't let the phrase 'that's not my goal' end the conversation. Treat it as the start of a deeper discussion about what the goal actually means, whether the assignment connects to it, and what the employee is willing to do for the team. And if you do that consistently, you'll either get alignment — or you'll surface a deeper mismatch that needs to be addressed. Luna: And that's a conversation worth having early, before resentment builds. Lucas: Exactly. Because the goal of management isn't to make everyone happy all the time. It's to get great work done while helping people grow. And sometimes those two things are in tension. Our job is to navigate that tension — honestly, respectfully, and with a clear framework.