How Do I Mentor Someone Else for the First Time?

To mentor someone for the first time, stop trying to be useful. Your instinct will be to hand over answers, because answers are what you are good at. The job is asking better questions, telling the truth about your own failures, and being reliably available for an hour a month. That is most of it.

The best technician on your floor usually makes the worst supervisor.

I have watched it happen more times than I can count, and I have been on the wrong end of it myself. Somebody is excellent at the work. Fast, accurate, the one everybody asks. So the company rewards them the only way it knows how, which is to put them over people.

And they fail. Not because they got worse at the work. Because being good at a thing and being good at growing somebody else in that thing are two completely unrelated skills, and nobody ever tells you that.

Mentoring is the same trap in a smaller package. Somebody asks you to mentor them, which feels like a compliment about your competence, and so you show up ready to be competent at them.

The Trap Every Good Technician Falls Into

Here is what it looks like. They bring you a problem. You know the answer. You give it to them. They say thanks. You both leave feeling good.

Nothing happened.

They got a fish. They did not get any better at fishing, and worse, they learned that the way to solve a problem is to bring it to you. You have made yourself necessary, which feels like being helpful and is actually the opposite.

I fell into this hard. I am a fixer by trade. Forty years of walking up to a machine that is down and making it run. When somebody brought me a problem, giving them the answer was not a decision, it was a reflex.

The shift that changed everything was small. Before answering, I started asking one question: what have you already tried?

Half the time they had already thought of the answer and just wanted somebody to tell them it was not stupid. That is a completely different conversation, and if I had jumped in with my answer I would have stolen it from them.

What to Do in the First Conversation

Do not prepare a curriculum. You are not teaching a course.

Spend the first meeting finding out what they actually want, which is usually not what they said in the email. Somebody who asks for help with "leadership skills" often means their peer got promoted and it stung. You cannot help with the first thing. You can help enormously with the second.

Then agree on something boring. How often, how long, who schedules it. Boring beats enthusiastic. A monthly hour that actually happens is worth more than a weekly hour you both cancel by week three.

Ask Instead of Answer

Your value is not your answers. It is that you have already been where they are, so you know which questions are worth asking.

When they describe a problem, resist for sixty seconds. Ask what they think is going on. Ask what they would do if you were not available. Ask what the other person in the story might say about it.

Then, yes, give your answer. You are not a therapist and withholding what you know is its own kind of arrogance. But give it as one option among the ones they generated, not as the verdict from on high.

And tell them your failures. Specifically, not vaguely. Not "I made mistakes too," which is useless. Tell them about the appointment you missed, the person you misjudged, the year you got it wrong. People cannot learn from your polished version. They can learn from the version where you looked foolish, because that is the version that resembles their Tuesday.

What If I Am Not Qualified for This?

You are more qualified than you feel and less qualified than they think, and both of those are fine.

Nobody needs you to have all of it figured out. They need somebody five or ten steps ahead who remembers what this part felt like. In fact being ten steps ahead is often better than being thirty, because you can still remember the details. The person thirty years ahead has forgotten what was hard.

Say the honest thing out loud in the first meeting. "I have not done the exact thing you are trying to do, but I have done something like it and I will tell you what I know and where I am guessing." That sentence buys you enormous room, and it models the exact behavior you want from them.

The one thing you do owe them is preparation. Five minutes before the call, look at your notes from last time and remember what they said they would do. Nothing signals "I do not really care about this" faster than making somebody re-explain their own life every month.

How Much Time Does This Actually Take?

An hour a month, plus about ten minutes of thinking around it. That is a real commitment and it is a small one.

The failure mode is not that people give too little. It is that they promise too much in the first flush of being asked, then quietly disappear in month three because they built something that did not fit their actual life. That disappearance does real damage, more than saying no would have.

So underpromise. Offer the hour a month you can genuinely protect, and protect it like you would a customer meeting. If it turns into more, wonderful. Nobody has ever been disappointed by a mentor who did more than promised.

And put an end date on the first stretch. Ninety days, then we both decide whether to keep going. That gives either of you a graceful exit if it is not working, which makes both of you more honest in the meantime.

Reflection Questions

1. When somebody brings you a problem, how long before you start answering?
2. What failure of yours would actually help this person, told specifically?
3. What did they ask for, and what do you suspect they actually want?
4. What amount of time can you protect every month without resenting it?
5. Are you making yourself useful, or making yourself necessary?

The Bottom Line

Mentoring somebody is not performing your competence at them. It is asking better questions than they can ask themselves yet, and showing up when you said you would.

This week, do one thing. In your next conversation with them, ask "what have you already tried" before you say anything else. Then be quiet long enough for a real answer.

The best technician makes the worst supervisor because nobody teaches them that growing people is its own trade. You get to skip that lesson. Being good at your work qualified you to be asked. It does not qualify you to answer, and knowing the difference is most of what makes a good mentor.

So here is my question for you. The last time somebody brought you a problem, did you help them think, or did you just hand them the answer and feel useful?