Coaching and mentoring are two ways of developing a person, and PMI lists both among the tasks of the People domain, alongside training and the support of team performance. The examination expects a candidate to tell them apart in a scenario and to choose the one the moment calls for. They run in opposite directions. Coaching draws the answer out of the person being coached, who is assumed to know more about their own situation than anybody else does. Mentoring passes on experience from somebody who has already done the thing.
What separates them is where the content comes from, which is why a peer can mentor and a senior person can coach. The sections below describe the two conversations, when each one fits, the technique each one needs and why the cheaper option wins under pressure and costs more later.
How the two conversations differ
In a coaching conversation the coach contributes structure, attention and questions. The content belongs to the person in front of them, including the constraints, the relationships, the history of what has already been tried and the definition of what a good outcome would be. A coach who has never worked in that domain can still coach well, which surprises people.
In a mentoring conversation the mentor contributes content. They have run a project like this one, made the mistake being described or know how the organisation actually approves an exception. The value is the experience itself, and a mentor who withholds it in an effort to sound non directive has wasted the meeting.
| What differs | Coaching | Mentoring |
|---|---|---|
| Purpose | Build the person's own capacity to work the problem | Pass on experience the person has no way of having yet |
| Who holds the answer | The person being coached | The mentor |
| The opening move | A question that hands the thinking back, such as what have you already tried | An account of what happened when the mentor stood in the same place |
| Domain experience | Optional, and a coach from outside the domain often works well | The whole of the contribution |
| Fits when | The person has the knowledge and something else is in the way | The gap is knowledge they could not reasonably have acquired |
| How it fails | Coy questions that withhold a fact somebody needed | War stories with no ask inside them, or advice given for a problem the mentor never heard properly |
| What is seen afterwards | The person works the next problem alone | The person can use the thing tomorrow, and knows when it applies |
Both differ from managing, which carries authority over the work, and from training, which delivers a defined body of material against a syllabus. A manager can coach and a trainer can mentor, and the confusion arrives when the manager's authority walks into the room with the questions.
When coaching fits and when mentoring fits
Mentoring fits when the gap is knowledge the person could not reasonably have. Somebody in their first month as a project manager should not have to discover through careful questioning how the change board works, and asking them what they think the answer might be is a small cruelty.
Coaching fits when the person has the knowledge and something else is in the way. A capable team lead who keeps missing the same commitment usually knows why, and so does the analyst who avoids raising risks in front of the sponsor. In both cases an answer supplied from outside gets agreement in the room and no change afterwards, because the obstacle was never information.
The test is simple enough to run in the moment. A project manager who genuinely does not know the right answer for this person in this situation is in coaching territory. One who does know, where the only reason the other person does not is that they have never been here before, should say so plainly.
Most real conversations move between the two. A mentor who supplies the missing fact about the change board and then asks what the person now wants to do has used both in ninety seconds, which is how the pair usually work in practice.
The coaching question
The core coaching move is a question that opens the thinking up. What is the real problem here, what have you already tried, what would you do if the sponsor said yes and what would have to be true for this to work are all of that kind. Each of them hands the thinking back.
A question with its answer hidden inside it is advice wearing a question mark, and people recognise it instantly. Have you considered talking to procurement belongs in that category. The difference shows in what happens next, because advice produces a nod and a real question produces a pause.
Silence is part of the technique. The useful answer often arrives several seconds after the comfortable one, and a coach who fills the gap never hears it.
The mentoring technique
The mentoring equivalent of a bad question is an unbounded story. An answer that helps names the situation the mentor was in, what they did, what it cost and what they would change, and it stops there so the other person can decide how much of it transfers.
The mentor asks what the person has already tried before supplying the answer, for a reason that has nothing to do with coaching purity. Half the time the other person's situation differs from the mentor's in a way that would have made the answer wrong, and the only way to find that out is to hear the situation first.
The conversation finishes with something specific enough to do. A mentoring conversation that ends in general encouragement has produced a pleasant half hour, and one that ends with a named person to speak to and a sentence to open with has produced a change.
Why telling wins under pressure
A project manager who has been asked a question already knows an answer, and telling takes ninety seconds while coaching takes twenty minutes. Under schedule pressure the arithmetic looks obvious, and over a single conversation it is obvious.
The cost lands later. A team coached through its problems solves the next one alone, and a team given the answer comes back with the next problem, so the telling habit steadily increases the load it was meant to relieve. This is why coaching is discussed as an investment, and why it collapses first on exactly the projects that most need it.
Coaching inside the Scrum Master accountability
The same pair of conversations arrives differently for a Scrum Master, because the coaching stance is named in the accountability itself. The 2020 Scrum Guide lists coaching the team members in self-management and cross-functionality among the services owed to the team, so a Scrum Master who only ever supplies answers has left part of the accountability undone.
Coaching is also most of what a Scrum Master has to work with, since the accountability carries no authority over the work and no power to assign a task. Telling a Developer what to do buys agreement in the room and changes nothing afterwards, and the delayed cost arrives inside the next Sprint.
Mentoring keeps its place, and the gap it fits is the framework itself. A team three Sprints in does not know what the Guide says about a timebox or a commitment, and establishing Scrum means helping everyone understand Scrum theory and practice, which is teaching. The line these assessments draw sits between the two gaps, so answering a question about how Scrum works discharges the accountability and deciding for the team how it will work exceeds it.
Coaching as an observable skill
Coaching is often described as a personality trait, which is a comfortable mistake because it excuses anybody who does not do it. It is a set of behaviours that can be watched, counted and improved.
The ratio of questions to statements across one conversation can be recorded. How long a silence is left before somebody fills it can be timed, and whether a question carried its answer inside it can be judged afterwards. All of that is measurable, every one of those measurements moves with practice, and that is what makes coaching a competence.