The GROW Coaching Model: How Managers Can Use It to Develop Their Teams

Knowing about the GROW model is not the same as knowing what it actually asks of you as a manager.

Most managers who've attended leadership programs have encountered the GROW model. Some remember the acronym. Fewer have run a single conversation that actually followed the structure. And the ones who've tried often describe it as frustrating — they start with Goal, ask about Reality, and then either jump to their own solution or wait uncomfortably for the team member to come up with one.

The model isn't broken. The approach is. GROW works when the manager understands that their job in a coaching conversation is not to have the answer — it is to ask the question that makes the answer visible.

What Is the GROW Model?

Does your team come to you with problems, or with thinking? Do your one-on-ones feel like they change something, or do they mostly review what's already happening?

The GROW model is a structured coaching framework for managers, standing for Goal, Reality, Options, and Will. Developed by Sir John Whitmore and colleagues in the 1980s, it guides a coaching conversation that moves a team member through four stages: what they want to achieve, where they currently are, what options are available to them, and what they will commit to doing next.

Whitmore introduced the framework to organisations worldwide through his 1992 book Coaching for Performance, which has since sold over a million copies. It is today the most used coaching model in the world. When Google's Project Oxygen research identified "being a good coach" as the single most important behaviour of a highly effective manager, the GROW model was one of the tools Google built into its manager training to put that finding into practice.

The GROW model is not a script. It is a sequence — and each stage has a job that is entirely distinct from the others.

Why Most Managers Already Coach — Just Badly

How many times in a typical week does a team member come to you with a problem? How many of those conversations end with you providing the solution? How different does that actually feel from what you'd call "coaching"?

The uncomfortable answer is that most managers think they coach because they talk about development and ask the occasional question. What they're actually running is advice-giving that looks like coaching from the outside but functions like instruction on the inside.

This is particularly sharp in the Indian corporate context. Managers are usually promoted for functional excellence — the best engineer, the most reliable ops person, the top sales performer. The instinct they've spent a decade building is to know the answer faster than anyone else in the room. Coaching asks them to do the opposite: to withhold the answer even when they have it, and to trust that the team member can find it themselves.

Not "here's what I would do" but "what have you already considered?"

Not "the issue is your stakeholder management" but "what do you think is making this difficult?"

A sales manager who tells a struggling team member "Go back to the customer with a revised proposal" hasn't coached. They've directed. The team member may execute this specific action well, but they haven't built the diagnostic muscle to handle the next difficult customer conversation independently.

A manager who always gives answers trains a team that always needs answers.

The Four Stages and Where They Actually Go Wrong

A product manager is struggling to get buy-in from the finance team for a new initiative. She comes to her manager after three weeks of unsuccessful meetings. Most managers will either share a relevant war story, or move straight to a specific recommendation. Neither is coaching.

Here is what the GROW model says to do instead — and where each stage typically breaks down in practice:

Goal — "What do you want from this conversation?" Most managers skip this and assume they know why the team member is there. But someone coming in frustrated about stakeholder resistance might want to think through whether the initiative is worth fighting for, or get a sounding board on the dynamics. Without naming the goal for the conversation itself, the discussion goes wherever the frustration takes it. Establishing a clear conversation goal is the first, most underestimated job of GROW.

Reality — "What is actually happening right now?" This is the stage Indian managers rush through the most. They hear "the finance team won't engage" and they're already preparing a solution. But a rigorous Reality stage — "What have you already tried?" "What's your read on what's driving their resistance?" — does something advice never does: it gives the team member the structured space to hear their own thinking clearly. People often already know the answer. They haven't been given the slow, attentive conversation to find it.

Options — "What could you do about this?" This is where the model either works or collapses. A manager who offers their preferred option the moment the team member pauses has ended the coaching conversation. The job at this stage is to generate multiple possibilities — not evaluate them — by asking: "What else could you try?" "What would you do if the obvious route wasn't available?" Three possibilities before any evaluation: that's the standard a good coaching conversation holds to.

Will — "What will you actually do, and by when?" Most conversations end at Options without a real commitment. The team member leaves with a useful set of ideas and no specific next step. The Will stage closes the loop — not by the manager assigning the action, but by the team member choosing their own and naming a timeline. "What are you committing to?" is a different question than "What do you think you'll try?"

Most managers jump from Reality straight to Will — skipping Options entirely — and then wonder why the same problem comes back next month.

Programmes that build the manager-as-coach habit — like GlobalGyan's people manager journeys — work because they practise these conversational moves across real-world scenarios, not just teach the framework.

The Questions That Make GROW Work

Are you asking questions that open possibilities, or questions that funnel toward your answer?

The quality of a GROW conversation is determined by the quality of the questions. And the difference between a question that coaches and a question that leads is usually subtle — it is in whether the manager already knows the answer they want the team member to give.

A practical question bank at each stage:

The question that unlocks the Options stage is "What else?" — not "Have you thought about X?" The first invites the team member's thinking. The second redirects toward yours.

An operations manager coaching someone stuck on a supply chain delay who asks "What else could you do?" for the third time, and waits silently, will get a response that neither of them expected at the start of the conversation. That response is more useful than any recommendation the manager could have made.

The best GROW question is usually the simplest one — and the one the manager finds hardest to let hang in the room without filling it.

How to Use the GROW Model in Your One-on-Ones

So what changes in practice when you start running genuine GROW conversations with your team?

The first thing you notice is that the conversation feels slower. A coaching conversation is structurally designed to resist the manager's instinct to resolve quickly. That discomfort is the signal it's working.

The second thing you notice, over weeks, is that your team starts arriving with less-raw problems. A team member who has been consistently coached doesn't walk in saying "I don't know what to do about the vendor issue." They walk in saying "I see two or three routes on the vendor issue — can we stress-test them?" That is a meaningful shift, and it compounds. It's the shift from a team that depends on the manager's judgment to one that's building its own.

The practical entry point is not a scheduled coaching session. It's your next one-on-one. Pick one problem a team member raises and resist the instinct to solve it. Name the goal for the conversation. Ask what they've already tried. Ask what else is possible. Ask what they're committing to. Twenty-five focused minutes done with that intent will change more than an hour-long "development discussion" that was really you presenting your thinking with questions in between.

For managers wanting to build this habit with more structure, GlobalGyan's first-time manager program and the broader leadership journeys build coaching conversations as an applied skill — practice that goes beyond the framework and into the room where the conversation actually happens.

A manager who coaches well gradually makes themselves less necessary for their team's decisions — and far more necessary for their team's growth.

Frequently Asked Questions

1. What does GROW stand for in coaching? GROW stands for Goal, Reality, Options, and Will (sometimes called Way Forward). Goal names what the team member wants to achieve in the conversation, Reality maps where they currently are, Options generates possible courses of action without evaluating them prematurely, and Will pins down a specific commitment to a next step, with a timeline attached.
2. How do I know if I'm coaching or just advising? The clearest signal is who does most of the talking. In a genuine coaching conversation, the team member should be speaking for roughly 70-80% of the time, with the manager asking questions rather than sharing perspective. If you finish the conversation having offered your analysis, your recommendation, or your experience of a similar situation, you advised. If you asked questions that helped the team member identify their own path forward, you coached.
3. Can the GROW model work with experienced or senior team members? Yes — and often it works better, because experienced professionals have more to draw on in the Options stage. The key is framing: not "let me coach you" but "I want to think this through with you by asking questions rather than giving my view." Most senior team members engage well once they understand the intent. Resistance usually comes when it feels imposed rather than offered.
4. My team just wants answers from me — they don't respond well to being asked questions. What do I do? This is almost always a pattern the manager created, not a fixed preference. Teams that want answers have usually learned — correctly — that the manager provides them faster and better than they can on their own. Name the shift explicitly: "I'm going to start asking you more questions instead of giving my view — because I want you to build your own thinking here." Most teams adapt within a few weeks, and the resentment of being questioned instead of helped disappears once the team member experiences that the questions are genuinely useful.
5. How long does a GROW coaching conversation take? A focused GROW conversation fits comfortably in 20 to 30 minutes inside a one-on-one. Goal typically takes 2-3 minutes, Reality 8-10 minutes (the most valuable phase), Options 6-8 minutes, and Will 3-5 minutes. The most common structural error is spending too long in Reality and running out of time for Options and Will — which leaves the conversation feeling rich but inconclusive.