One of the first people I managed used to come to me stuck, and I loved it, because being the person with the answer felt like the whole job. He would describe a problem, I would tell him what I would do, he would nod and go do it. It worked, in the sense that the problem got solved each time. It failed, in the sense that a year later he was still bringing me the same class of problem, because I had spent that year answering instead of developing. I thought I was mentoring him. I was just doing his thinking out loud and calling it leadership.
That confusion, between helping someone and developing someone, sits underneath most of how new managers get coaching and mentoring wrong. They are not the same activity, they do not produce the same result, and using one when the moment called for the other is one of the quietest ways a manager keeps a capable person dependent or leaves a struggling one without what they actually needed.
This article is one cluster under the Leadership Skills hub. The leadership skills for new managers pillar guide covers developing others as skill five, alongside the other nine. The pillar makes the case that developing your team is the skill most new managers value and fewest actually practice. This cluster goes deep on the specific fork inside it: coaching versus mentoring, what each one is for, how to tell which a person needs right now, and the two mistakes that look like development but are not.
If the person in front of you is not just stuck but consistently underperforming, the question may not be coaching or mentoring at all. The Should I Put This Employee on a PIP? free decision tool helps you triage whether you are looking at a development gap (which coaching or mentoring can close) or a performance problem that needs a different track entirely, before you spend weeks on the wrong one.
The actual difference
Strip away the jargon and the distinction is clean.
Coaching helps a person solve their own problem. It is mostly asking, not telling. You ask questions that pull the answer out of them: what have you tried, what would you do, what is actually in the way. The content comes from them. Your job is to create the thinking, not supply it. Coaching is usually about a present, specific work problem, and its payoff is that the person gets better at solving that class of problem without you next time.
Mentoring shares accumulated wisdom. It is mostly telling, in the good sense: a more experienced person offering pattern recognition, perspective, and hard-won judgment that the other person has not had time to develop yet. The content comes from you. Mentoring is usually about the bigger picture, career and identity and direction, and its payoff is that the person sees around a corner they could not have seen around alone.
The cleanest way to hold it: coaching helps someone solve the problem in front of them; mentoring helps them figure out which problem is worth working on in the first place. One draws out, the other passes down. Most direct reports need both from you, in different ratios, at different moments. The skill is knowing which the moment is asking for.
How to tell which one a person needs
The mistake is treating this as a personality setting (“I’m a coaching manager”) rather than a read on the situation. The same person needs coaching on Tuesday and mentoring on Thursday. Three signals tell you which:
Do they have the raw material to find the answer themselves? If the person has the experience and context to reason their way to a good answer but is looking to you out of habit or low confidence, that is a coaching moment. Asking will surface what they already know. If they genuinely lack the experience to know what good even looks like, asking “what would you do?” is not coaching, it is withholding, and it will land as you being unhelpful on purpose. That person needs you to share the pattern, or to teach the skill outright.
Is the question about the work, or about the path? “How should I handle this stalled project” is usually a coaching question, because the answer lives in the specifics they hold. “Should I be aiming for a management track or staying technical” is a mentoring question, because the value is in your perspective on a road they have not walked yet. Match the move to the altitude of the question.
Where are they on this specific task? This is the same calibration as in the situational leadership cluster, applied to development: someone new and uncertain on a task needs more telling (teaching, then mentoring); someone capable but cautious needs more asking (coaching to build their confidence in judgment they already have). Read the development level, then pick the move.
The two mistakes that look like development
Mistake 1: Mentoring when they needed coaching
This is the one I made, and it is the more common of the two, because it feels good. Someone brings you a problem they could solve themselves, and you solve it for them, dressed up as sharing your experience. Every time you do it, you teach them that the fastest path is to bring it to you, and you rob them of the rep that would have made them better. The team gets more dependent, your queue gets longer, and it all feels like helpfulness.
The tell: you are doing most of the talking in conversations where the other person already had the answer. The fix is to make “what would you do?” your reflex before “here’s what I’d do,” and then to actually wait through the silence. This is the asking-not-telling discipline from the active listening cluster, pointed at development. Half the time they had the answer and needed permission to say it out loud. The other half, the gap between their answer and yours is the real conversation, and far more useful than your unilateral take.
Mistake 2: Coaching when they needed mentoring or teaching
The opposite error, and the one that arrived once managers learned that coaching is good. You take someone who genuinely does not have the experience, and you “coach” them with open questions, and they flounder, because there is nothing to draw out yet. Asking a true beginner “what do you think the right approach is?” is not developmental. It is frustrating, and it can read as a manager hiding the ball. That person needs you to teach the system or share the pattern first, and the coaching comes later, once they have the raw material to reason with.
The tell: your questions are met with anxious guesses or visible relief when you finally just tell them. When that happens, switch modes. Mentor or teach now, coach once the foundation is there.
How to actually do each one well
Coaching, done well, is three moves: ask an open question, wait through the silence (most managers cannot tolerate more than a couple of seconds and fill it, which closes the door), then ask one follow-up to whatever they said before offering anything of your own. The follow-up is where the real thinking happens. Only after that, if it is still needed, offer your view, clearly labeled as your view rather than the verdict.
Mentoring, done well, shares the pattern, not the prescription. The weak version is “here is exactly what to do.” The strong version is “here is what I have seen happen three times in this situation, and here is the variable I would watch.” You are handing them a lens, not an answer, so that next time they can apply the lens themselves. Mentoring that hands over conclusions creates the same dependence as over-coaching; mentoring that hands over judgment builds it.
Both depend on feedback to hold together. Coaching without feedback is just questions, and feedback without coaching is just judgment. The constructive feedback examples library and the guide on how to give feedback for the first time cover the in-between conversations that keep a development arc moving.
When it is neither
Sometimes the honest answer is that the person needs neither coaching nor mentoring right now. Two cases:
They need teaching. There is a straight skill or knowledge gap, and the developmental move is simply to train them on the system or the tool. Do not romanticize this into coaching. Teach the thing, then develop the judgment around it afterward.
They need a different track entirely. If the gap is wide and persistent, and you have genuinely coached and mentored and taught, you may be in performance-management territory rather than development territory. The coaching an underperforming employee guide covers the line between a development conversation and a performance one, and the PIP decision tool linked above helps you tell which side of it you are on before you commit weeks to the wrong approach.
How to start this week
Pick one direct report and one recent conversation, and ask yourself honestly: did they need coaching, mentoring, or teaching, and which did I actually give them? Most managers find at least one mismatch immediately, and it is usually the first mistake: mentoring (answering) someone who needed coaching (thinking).
Then, in your next 1-on-1, run the coaching reflex once. When they bring something they want input on, ask “what would you do?” before offering anything, wait, ask one follow-up, and only then add your view if it is still needed. Notice how much of what they wanted turned out to be permission to articulate the answer they already had.
The deeper version of this skill, and how it sits among the other nine that compound for new managers, is in the leadership skills pillar guide under skill five. The line worth keeping is the one it took me a year and a too-dependent direct report to learn: helping someone solve today’s problem and developing someone are not the same act, and the difference is mostly whether the answer came from you or from them.