Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Reluctant Mentor on Your Team
Transcript
- Lucas: You've got a senior team member who's brilliant at their job. Deep expertise, great track record. So you ask them to mentor a junior hire. And they say — well, they don't say no exactly, but they find a dozen reasons to delay. Sound familiar? Luna: Very. I've seen that more times than I can count. Usually it's the person who's already drowning in their own work. Lucas: Right. And the natural instinct as a manager is to push harder — because mentoring is part of their role, right? But that often backfires. So today I want to dig into one specific case — a principal engineer named Diane at a mid-sized SaaS company. Her manager, Tom, needed her to mentor a new hire named Priya. Diane was the obvious choice. But she kept saying she was too busy. Luna: What was Tom's first move? Did he just assign it? Lucas: Almost. He scheduled a one-on-one and said, 'Diane, I need you to mentor Priya. Here's the plan.' And Diane's response was a list of reasons — her current project had a tight deadline, she was already mentoring two interns informally, she didn't think Priya needed that much hand-holding. All valid points on the surface. Luna: So Tom hit a wall. What did he do next? Lucas: He paused and asked two questions. First: 'What's really going on?' And second: 'What would make this work for you?' That shifted the conversation completely. Luna: I love that. It's not confrontational — it's curious. What did Diane say? Lucas: She admitted she was worried about three things. One: she didn't think mentoring would be recognized in her performance review — it felt like extra work with no upside. Two: she was afraid it would derail her own project timeline. And three: she didn't have a structure for it — she didn't know what a good mentoring relationship looked like. Luna: So the reluctance wasn't laziness or arrogance. It was fear of the unknown and lack of incentives. Lucas: Exactly. And that's the key insight — most reluctant mentors aren't bad people. They're unclear on the value proposition. So Tom's job became about reframing, not demanding. Luna: How did he reframe it? Lucas: First, he tied mentoring directly to Diane's career growth. He said, 'You've talked about wanting to move into a staff engineer role. That role requires influencing and developing others. This mentorship is a chance to demonstrate that skill.' Suddenly it wasn't a chore — it was a leadership development opportunity. Luna: That's smart. It connects the ask to her own ambition. Lucas: Second, he addressed the time concern. He offered to reduce Diane's meeting load by 20 percent for the next quarter — basically swapping two recurring meetings for a weekly thirty-minute mentoring slot. And he made sure her project manager knew about the adjustment. Luna: So he protected her bandwidth. That's huge. A lot of managers skip that step. Lucas: Third — and this is the one I think most managers miss — he created a lightweight structure. He gave Diane a simple mentoring template: a weekly check-in with three questions — what's going well, what's confusing, what are you working on next. No curriculum, no formal reviews. Just a conversation. Luna: That lowers the bar. It makes mentoring feel doable instead of daunting. Lucas: Exactly. So Diane agreed to try it for eight weeks. Tom also made sure to mention the mentorship during Diane's next performance review — he called out her contribution specifically. By week six, Diane told Tom she actually enjoyed it. She said Priya had asked a question that made her rethink her own approach to testing. Luna: That's the hidden benefit — mentors often learn as much as mentees. I've seen that firsthand. Lucas: So the big takeaway is: before you label someone as unwilling, diagnose the resistance. Is it time? Is it recognition? Is it a lack of structure? Then address each one specifically. Luna: And don't assume they know how to mentor. Even the best engineers need a framework. Lucas: That's right. One more thing Tom did that I think is worth highlighting — he checked in after the first month. He asked Diane how it was going and whether she needed any support. That follow-up signaled that he wasn't just delegating; he was invested in her success as a mentor. Luna: That builds trust. And it also gives you a chance to course-correct if something's off. Lucas: Yeah. So to summarize the playbook: one, reframe mentoring as a growth opportunity for the mentor. Two, protect their time — remove something else from their plate. Three, provide a simple structure. And four, follow up. Luna: If you're a manager listening, and you've got a reluctant mentor on your team, I'd start with that one-on-one. Ask the curious questions before you make the ask. Lucas: And if you've ever been the reluctant mentor yourself — I think we all have at some point — this episode might give you a new lens on it. Luna: Absolutely. You know, Lucas, conversations like this are exactly why listeners tell us they value this show — it's practical, not theoretical. Lucas: And if you find these episodes helpful, you can support the show at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. It helps us keep the podcast ad-free and focused on real-world management challenges. Luna: Yeah, it's a small gesture that makes a big difference for us. Lucas: So back to Diane — eight weeks in, she volunteered to mentor another junior engineer. Tom didn't have to ask. That's the win. Luna: That's the ultimate sign that the approach worked. Lucas: For next time, think about a team member who might be a hidden mentor — someone who hasn't been asked or hasn't had the right structure. You might be surprised. Luna: Good thought. See you next Monday.