The Manager as Coach: Using Coaching Conversations in Everyday Management

Most managers tell. They have the answer — or something close to one — and the meeting is running over, and it is quicker to just say what needs to happen. The person in front of them nods, goes away, and either does the thing or doesn’t. And the next time a similar situation comes up, they come back for another answer. The cycle repeats. The manager accumulates decisions; the employee accumulates dependency. Nobody planned it this way. It just drifted there.

This is not a character flaw. It is the natural result of managing in an environment that rewards output over development and where the path of least resistance is to be the person with answers. The problem is that it has a ceiling. A manager who has made themselves the answer machine for their team has built something that cannot function without them, and which cannot grow much beyond whatever they can personally oversee.

Coaching conversations break that pattern. Not formal coaching sessions — most managers are not professional coaches and should not pretend otherwise — but a particular kind of conversation that helps the other person think for themselves rather than lean on yours. This is what it means for a manager to “coach.”

Why telling feels efficient and often isn’t

When an employee comes to you with a problem, the telling response is fast. You explain what to do, they go and do it, the problem is resolved. Ten minutes all in. The coaching response — asking questions, drawing out their thinking, resisting the urge to give the answer — takes longer and can feel frustrating when you know exactly what the right outcome looks like.

But the calculation shifts when you think about what each response produces. The telling response resolves one problem. The coaching response builds the capability to resolve the next ten. If you can get someone to the point where they work through a problem systematically and arrive at good answers on their own, you have returned far more of your time than you spent.

There is also a less obvious effect. People who are told what to do do not feel ownership over the outcome in the same way as people who reached the solution themselves. The employee who was coached to a decision is more committed to it, more likely to adapt when something goes wrong, and more likely to apply the same thinking next time without coming back to you at all.

The caveat: this is not an argument for coaching everything. There are situations where telling is exactly right — emergencies, tasks where there is one correct answer and no developmental value in discovering it slowly, situations where the person genuinely does not have the foundation to reason their way to a useful conclusion. A new starter learning a regulatory process does not need to be coached towards the answer. They need to be told the answer and shown why it is the answer. The skill is knowing which situation you are in.

What a coaching conversation actually looks like

A coaching conversation does not require a whiteboard, a model, or a scheduled session. Most of them happen in passing — in a corridor, at the end of a team meeting, in the two minutes before a call. They are distinguished not by their setting but by the kinds of questions the manager asks.

Consider two versions of the same scenario. An employee comes to you and says: “I’ve got a difficult client call tomorrow. I’m not sure how to handle the pushback on the pricing.”

Telling version: “The key is to anchor on value before you get into the numbers. Start with what they’ve told you they need to achieve, then connect the pricing to that outcome. If they push back on the cost, ask them what it would cost them to not solve the problem.”

Coaching version: “What do you know about why they are concerned about the pricing?” [Employee responds] “What have you tried in similar conversations before that worked?” [Employee responds] “If you could run it perfectly, what would that look like?” [Employee responds] “What’s the thing you’re most unsure about?” [Employee responds] “So what do you think you’ll do?”

Both conversations can end with the same practical outcome. The difference is who did the thinking. In the coaching version, the employee has articulated what they know, connected it to previous experience, and committed to an approach they reasoned out themselves. They are more prepared, not less — and next time a difficult client call comes up, the first call they make is to themselves.

The GROW model: a useful frame without the fuss

If you have read anything about workplace coaching, you will have encountered the GROW model — Goal, Reality, Options, Will. It is useful not because it is profound but because it gives you a mental sequence to work through when a conversation is getting circular.

Used in a formal coaching context, GROW is a structured process. Used informally by a manager, it is more like a loose checklist:

Goal: Are we clear about what they are trying to achieve? Not the immediate task, but the outcome they need.
Reality: Do they have an accurate picture of where things actually stand? What do they know, and what might they be assuming?
Options: Have they thought through more than one approach? Are they stuck on the first option because it is familiar?
Will: What are they actually going to do? Have they committed to something specific?

The value of keeping this in the back of your mind is that it stops you from giving advice at the Options stage before the person has established a clear Goal or an honest Reality. “Have you thought about trying X?” said too early often lands in a vacuum, because the person is still working out what problem they are actually trying to solve.

You do not need to use the labels. You do not need to announce that you are “doing GROW.” The framework is a prompt for you, not a script.

When not to coach

This deserves its own heading, because the most common mistake made by managers who have recently been introduced to coaching is to apply it indiscriminately.

Do not coach when:

The situation is urgent. A fire is not a coaching moment. Tell people what needs to happen and debrief afterwards if there is developmental value in it.
You need a specific outcome and the path to it is well-defined. Some tasks have a right answer. Sending someone off to discover it through questioning is not developing them; it is wasting their time.
The person is in distress. Someone who is overwhelmed, upset, or in crisis needs to feel heard first. Asking “so what options do you see?” when someone is struggling can feel dismissive rather than empowering.
You would need to pretend you do not have an answer. Socratic questioning from someone who clearly knows the answer and is withholding it is transparent and annoying. If you know what the right answer is and they genuinely do not, just tell them — ideally with the reasoning attached so they have something to learn from it.
There is a safety or compliance issue. This is not a moment for exploration. It is a moment for clarity.

The manager who coaches everything is just as unhelpful as the manager who tells everything. The goal is to develop the judgment to know which is called for.

The questions worth keeping

Coaching conversations hinge on questions more than answers. Some questions are reliably more useful than others — not because they are clever, but because they open up thinking rather than closing it down.

Questions that tend to work:

“What have you already tried?”
“What’s your read on what’s really going on here?”
“What would you do if you couldn’t come to me?”
“What are you assuming that might not be true?”
“If you had to pick one option, which feels most right and why?”
“What’s the risk of doing nothing?”
“What do you need from me right now — advice, a sounding board, or something else?”

That last one is underused and worth making a habit. It is surprising how often people come to a manager wanting to think aloud rather than to receive advice, and how often the manager leads with advice because that is the default mode. Asking what kind of support they need recalibrates the conversation before it has started on the wrong foot.

Questions that sound like questions but aren’t:

“Have you thought about just telling them directly?” — this is a suggestion wearing a question mark.
“Don’t you think you should…?” — same problem.
“Wouldn’t it be better to…?” — same.

These are fine in a telling conversation. In a coaching conversation, they undermine the whole point: they lead the person to your conclusion rather than theirs.

Making it a habit, not a session

The hardest part of becoming a coaching manager is not learning the techniques. It is building the habit of defaulting to questions rather than answers — and doing it in the normal flow of work, not just in scheduled development conversations.

A few things that help:

Pause before answering. When someone brings you a problem, resist the instinct to respond immediately. Even a two-second pause — “let me think about that” — creates space to choose your response rather than default to it. Often that pause is enough to shift from “here’s what I’d do” to “what’s your instinct here?”

Make it explicit, early. Tell your team that you will often respond to questions with questions, and explain why. “I want you to be able to solve these things without me” is not a rebuff — it is a statement about what you think they are capable of. Said clearly and early, it shifts the expectation so that coaching questions do not feel like obstruction.

Debrief after events. The most natural coaching conversations often happen after something has gone well or badly. “What would you do differently?” and “What did you learn from that?” are coaching questions. They require no model and no formal setup.

Accept slower, short-term. The first few times you coach rather than tell, the conversation will probably take longer. That is fine — it is an investment. The time comes back when the person stops needing you for that category of decision.

The managers who get this right are not the ones who master every coaching technique. They are the ones who became genuinely curious about how their people think, and who learned to hold their own opinions lightly enough to make space for someone else to find theirs.

If you want a structured development path for managers building a coaching style, SkillsCircle offers CPD pathways that combine coaching skills with wider people management practice — worth a look if your organisation is developing managers at scale.