Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Who Keeps Saying I Need a Mentor
Transcript
- Lucas: So Luna, last week I had a one-on-one with one of my engineers, and she said something I've heard a lot lately: 'I need a mentor.' And I realized I didn't have a good answer. Luna: What did you say? Lucas: I said I'd get back to her. And then I spent the weekend thinking about what she actually meant. Because 'I need a mentor' can be code for so many different things — sometimes it's about career direction, sometimes it's about skill gaps, sometimes it's just loneliness at work. Luna: Right. And if you just say 'go find a mentor' without any structure, it's like telling someone to go find a friend. It's not that easy. Lucas: Exactly. And there's real data on why unstructured mentoring fails. A 2025 study from the Association for Talent Development found that mentoring programs with clear goals and a defined timeline were twenty percent more effective at driving promotion rates than those that were just, you know, 'match people and see what happens.' Luna: Twenty percent. That's not trivial. So structure matters — but what does structure actually look like on the ground? Lucas: The first thing I tell managers is to ask the employee what outcome they're hoping for. Do they want to move into leadership? Master a specific technical skill? Understand the politics of the organization? Because a mentor for each of those looks completely different. Luna: So it's not just one mentor per person for all time. It's more like a specific project with a clear scope. Lucas: Exactly. I've seen it work well when you treat it like a short-term assignment. Three to six months, with a few specific goals. For example, one of my friends manages a data team at a mid-sized fintech, and they had a junior analyst who kept saying she needed a mentor. They paired her with a senior data engineer for exactly ninety days, with the goal of getting her comfortable with their cloud infrastructure. She went from constantly bugging the senior team for help to running her own pipeline deployment by the end. Luna: And the senior engineer didn't feel like it was a huge burden either, because it was time-boxed and had clear milestones. Lucas: Exactly. And that's key — because the biggest objection I hear from managers is 'I don't have time to be a mentor.' But if you define it as ninety minutes a month for three months, that's manageable. And it's not just the mentee who benefits. The same study found that mentors were promoted at twice the rate of non-mentors within a year. So it's actually a career accelerant for the mentor too. Luna: Twice the rate. That's a powerful argument to make when you're asking a senior person to take someone under their wing. Lucas: So the first step is to clarify what the employee actually needs. Then you can map that to a mentor who has the right experience, and you set up a formal agreement with goals, a timeline, and a check-in process. It's a lot more work up front, but it saves everyone from a vague, unproductive relationship. Luna: And what if there isn't an obvious internal mentor? What do you do then? Lucas: That's a great question. In smaller companies, or in specialized roles, the right mentor might not exist internally. In that case, a peer mentor — someone one or two levels ahead — can be just as effective, especially for learning organizational norms. Or you can look for an external mentor through professional networks. I've seen some companies create a small budget for external mentorship, and it pays for itself pretty quickly. Luna: And you mentioned the check-in process. What does that look like? Lucas: A quick fifty-minute check-in at the halfway point. You sit down with the mentee and the mentor together, and you ask three questions: What's working? What's not? And are we hitting the goals? If it's not working, you adjust — maybe change the goals, maybe change the mentor. That's the agile approach to mentoring. Luna: I like that. And it also gives you, as the manager, a way to stay in the loop without micromanaging the relationship. Lucas: Exactly. And one thing I want to be careful about is the difference between mentoring and managing. A mentor is not a spare manager. They're not there to approve time off or review performance. They're there for the stuff you, as the manager, might not be best positioned to provide — career navigation, political savvy, technical depth outside your domain. Luna: So if an employee comes to you and says they need a mentor, part of your job is to help them understand what a mentor can and can't do for them. Lucas: Right. And that's a conversation in itself. I had an employee once who was frustrated because she thought a mentor would solve her visibility problem. But what she actually needed was practice presenting her work to stakeholders. A mentor could help her prepare, but she had to do the presenting. So we reframed it as a combined approach: the mentor coached her on the presentation, and I made sure she got the opportunity to present at the next department meeting. Luna: That's a nice example of how you as a manager can still be involved without being the mentor yourself. Lucas: Yeah. And it's also why I think managers shouldn't try to be the sole provider of development. You can't be everything to everyone. But you can be the architect of their development network. Luna: Architect of a development network. I like that phrase. So when you're setting up a mentoring relationship, what are the practical steps you'd recommend to a first-time manager? Lucas: First, have the clarifying conversation. Second, identify a short list of potential mentors. Third, approach the mentor with a specific ask — 'Would you be willing to meet once a month for three months to help this person with X?' And fourth, set up a shared document where all three of you can track goals and progress. Luna: And what about the mentee's responsibility? They're not just passive recipients, right? Lucas: No, absolutely not. The mentee should drive the agenda for each meeting, come with questions, and be open to feedback. In fact, I'd go so far as to say the mentee should take the lead on scheduling and setting the agenda. That way the mentor isn't doing the heavy lifting. Luna: So it's like a mini-project where the mentee is the project manager. Lucas: Exactly. And I'd add one more thing: don't overlook internal resources that might already exist. Many organizations have formal mentoring programs or access to external platforms. As a manager, you don't have to reinvent the wheel. Just figure out what's available and how to plug your employee into it. Luna: And speaking of not reinventing the wheel — you know, this whole conversation reminds me of something. We spend so much time giving advice on managing people, and we hear from a lot of listeners who say it's helped them navigate tricky situations. If you've found value in these episodes, and you want to see us keep doing this ad-free, you can support the show at buy me a coffee dot com slash fexingo. It's a simple, no-pressure way to keep the lights on. We appreciate everyone who's contributed. Lucas: Yeah, we really do. Listen, we get it — money's tight for a lot of people. But if you're in a position to chip in, it helps us keep making these episodes. And it's easy to find: buy me a coffee dot com slash fexingo. Now, back to mentoring. One more thing I want to talk about, Luna, is how to know if a mentoring relationship is actually working. Luna: What metrics do you look at? Lucas: Beyond the simple check-in, I like to look at progress on the specific goals we set at the beginning. If the goal was to master a skill, there should be some demonstration of that skill — maybe a presentation, a code review, a project deliverable. If the goal was to increase visibility, then we should see the employee taking on more visible assignments. It's not just about feeling good. Luna: And that also ties back to the employee's own growth. If they're not progressing, you need to ask whether the match is right or whether the goal was the right one. Lucas: Exactly. And sometimes the mentoring relationship evolves into something longer-term, and that's fine. But the initial structure should be time-boxed, so you have a natural point to evaluate and decide whether to continue, change course, or end it gracefully. Luna: That's a good place to leave it. For our listeners, if you're a manager and an employee says they need a mentor, don't panic. Have the clarifying conversation, set up a structured match, and check in mid-way. You'll be surprised how much of a difference it makes. Lucas: And remember, a mentor is just one piece of the development puzzle. You're still the manager, and you still have a role in their growth. But you don't have to do it all alone. Thanks for joining us on Manager Mondays. We'll be back next week with another real-world problem to solve.