Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Who Always Says I Need More Challenge
Transcript
- Lucas: There's this moment every manager knows — the employee who's been a rock star for two years sits down and says, 'I need more challenge.' And your stomach drops a little, because you know what that can mean. Luna: Right, because it's never just about the workload, is it? It's the thing people say right before they start updating their résumé. Lucas: Exactly. And the worst reaction is to panic and pile on more tasks. I've seen that fail so many times. More work isn't the same as more challenge. The employee ends up more stressed, not more engaged, and they leave anyway. Luna: So what's the better move? How do you actually respond when someone says those words? Lucas: First, you have to understand what 'more challenge' actually means. In my experience, it's rarely about the volume of work. It's about one of three things: a need for more responsibility, a need for more visibility into the bigger picture, or a need for more skill development. Luna: That's helpful. I've definitely heard that phrase and assumed it was about responsibility, but visibility and skill development can look really different. Lucas: Right. Take a case I saw at a mid-sized software firm. A senior engineer named Priya was one of their best — shipping features, mentoring juniors, all that. And she told her manager she needed more challenge. The manager's instinct was to give her the next big project. But when they sat down and actually unpacked it, Priya said she wanted to understand how her team's work connected to the company's revenue goals. She didn't want more tasks, she wanted more context. Luna: So the manager was about to throw her into the deep end, but she just wanted to see the whole pool. Lucas: Exactly. That's a much easier fix, right? You can bring her into a strategy meeting, share some numbers, maybe let her present to leadership. But if you don't ask, you'll never know. Luna: And that's a great lead-in to something else. Since we're talking about what keeps people engaged, I want to say a quick thing about how we keep this show going. We don't run ads, and that's a deliberate choice — it keeps everything we talk about independent. A small group of listeners already chips in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these episodes. It's not a big ask, just a heads-up that if you've gotten value from these conversations, that's the one way to keep them coming. Lucas: Yeah, and it's genuinely appreciated. It lets us stay focused on topics like this without worrying about sponsors. So, back to Priya — what's the framework for having that conversation? Lucas: The 'challenge conversation' has three core questions. First: 'What part of your work feels most routine?' That gets them to be specific. Second: 'What would you like to have more of — ownership, context, or skill? That's the diagnostic. And third: 'What impact would that have on you and on the team?' Luna: I like that it's a two-way thing. You're not just extracting a wish, you're asking about the impact, which makes it a business conversation. Lucas: Exactly. And it's important to prepare for that meeting. Don't wing it. Think about what you've observed — where they shine, where they seem to lose energy. The more specific you can be, the better the conversation. Luna: So what if they say they want more ownership? How do you give that in a way that's safe for the team? Lucas: That's where you need to be strategic. You can't just give away a whole project or a client relationship without guardrails. But you can offer a 'stretch assignment' — something that's slightly beyond their current comfort zone but with clear support and checkpoints. For instance, let them lead a cross-functional initiative with a senior mentor as a safety net. Luna: So it's not an all-or-nothing leap. It's a controlled experiment. Lucas: Right. And you should set a timeline — maybe ninety days — and then review. That way, if it's not working, you can adjust without it feeling like a failure. Luna: And what if they say they want more context—like Priya? How do you scale that without putting them on the BCC of everything? Lucas: That one's about exposure. Start with a few things: invite them to a strategy review, share quarterly business reviews, or ask for their input on a business case. The point is to let them see how their work fits into the bigger picture. You can also assign them to shadow a leader for a day or two. Luna: That sounds like a low-cost way to boost engagement without a reorg. Lucas: Exactly. And if they want skill development, that's the easiest one. It's a conversation about courses, conferences, or stretch projects that teach a new technical skill or a soft skill like public speaking. You just have to make it concrete. Luna: Okay, so we've covered the diagnostic. But what about the manager who's thinking, 'I don't have time for this — I have a team to run'? Lucas: Fair point. But think about the time you'll spend recruiting and onboarding someone if they leave because they were bored. That's easily a few months of your life. An hour of honest conversation is a fraction of that. Luna: And it has a side benefit — it shows you care about their development, which builds trust across the whole team. Lucas: Absolutely. And there's a second part to this, which is what you do after the conversation. You need to follow through. If you promise to get them more visibility, book the meeting while you're still in the room. If you're going to offer a stretch assignment, sketch out the first steps right then. Follow-through is where most managers drop the ball. Luna: That's a good point. It's not just about the chat, it's about the action plan. Lucas: And one more thing — don't frame this as a one-time fix. Check in regularly. Maybe every month, ask a light version of the same questions. 'How are you feeling about the challenge level?' That way, you catch issues before they escalate into a resignation. Luna: So it becomes part of your ongoing management rhythm, not a crisis intervention. Lucas: Exactly. And that's the key takeaway: when someone says 'I need more challenge,' it's a signal, not a threat. Your job is to decode it. And the decode is always specific — it's about responsibility, context, or skills. Luna: I think this episode could save a few managers from losing their best people. Thanks for mapping it out, Lucas. Lucas: Thanks, Luna. And to our listeners — the next time you hear those words, take a breath, ask the three questions, and you'll be surprised how often the fix is simpler than you feared.