GROW Model

The GROW model is the most widely taught coaching framework in the world. It provides a simple four-step structure for a developmental conversation: clarify the Goal, examine the current Reality, generate Options, and commit to a Way forward (or Will). The power of GROW is less in the specific structure and more in the discipline it imposes: the coach asks more than they tell, and the coachee leaves with their own plan rather than their coach's prescription.

Origin

Graham Alexander developed the GROW model at Inner Game and Performance Consultants in the early 1980s. It was popularized by Sir John Whitmore in Coaching for Performance (1992), which sold over a million copies and became the foundational text for the professional coaching field. Whitmore's background was as a racing driver and sports coach; he applied sports-coaching principles (asking questions to help the athlete self-diagnose) to executive and workplace coaching. GROW is now taught in most formal coaching certifications (ICF, EMCC, CoachU) and is standard in corporate coaching training at companies like Google, Microsoft, and most of the Fortune 500.

The Framework

G - Goal:    What do you want? (specific, meaningful, achievable)
R - Reality: What is the current situation?
O - Options: What could you do? (generate multiple)
W - Will:    What will you do? (commitment, next step)

Each step is driven by questions, not statements:

Goal Questions

"What do you want to achieve from this conversation?"
"What would a successful outcome look like?"
"If we solve this, what changes?"
"What's the goal behind the goal?" (useful to find the deeper motivation)
"On a scale of 1-10, how important is this to you?"

Reality Questions

"What's happening now?"
"What have you already tried?"
"What's the impact on you? On others?"
"Who else is involved?"
"What resources do you have?"
"What's really in your control here?"

Options Questions

"What could you do?"
"What else? And what else?" (the most powerful coaching question)
"If there were no constraints, what would you do?"
"What's one option you've dismissed? Why?"
"What would [a person you admire] do in this situation?"
"What advice would you give a friend in your position?"

Will Questions

"Which option will you try?"
"When will you take the first step?"
"How will you know it's working?"
"What might get in the way? How will you handle it?"
"What support do you need?"
"How committed are you to this, 1-10?"

The structure is linear, but the conversation is iterative — it is normal to loop back to Reality after exploring Options, or to revise the Goal once Reality is clearer.

How to Use It

The Coaching Stance

Before using GROW, set your stance:

1. You are not here to solve their problem. You are here to help
   them solve it.
2. They have more context on their situation than you do. Trust it.
3. Your questions are for them, not for you. "Why did you do that?"
   is often a judgment disguised as a question.
4. Silence is okay. Let them think.
5. Resist the urge to suggest. The moment you suggest, they stop
   thinking.

Running a GROW Conversation

1. Set context (1-2 min):
   "You have 30 minutes. What would you like to focus on?"
   "What would make this time valuable?"

2. Goal (5-10 min):
   Explore what they actually want. Often the stated goal is not
   the real goal.

3. Reality (10-15 min):
   Help them describe the situation fully. What's working?
   What's not? What have they tried?

4. Options (10-15 min):
   Generate options. Breadth first, then depth. Push past the
   first two or three.

5. Will (5 min):
   Commit to a specific next step. Not "I'll think about it."
   Concrete action, by when, with what accountability.

6. Close (1 min):
   "What's your takeaway from this conversation?"
   "How will you remember this?"

A full GROW conversation fits in 30-45 minutes. Shorter "GROW moments" (5-10 minutes) work inside broader 1:1s for specific topics.

Tech & Company Example

A tech lead is having a 1:1 with a senior engineer who is frustrated about not getting promoted to staff.

Tech Lead (G - Goal):
  "What would you like to focus on today?"

Engineer:
  "I want to talk about the promotion. It didn't happen again, and
   I'm frustrated."

Tech Lead:
  "That sounds hard. What would success from this conversation
   look like for you?"

Engineer:
  "I guess... a clearer picture of whether this is going to happen
   and what I need to do."

Tech Lead:
  "Got it. What's the goal behind the goal — why does Staff matter
   to you?"

Engineer:
  "Because I feel like I'm doing the work and it's not being
   recognized. And the compensation gap is real."

Tech Lead:
  "So two things: recognition and comp. Are those equally important
   or is one more?"

Engineer:
  "Recognition, honestly. I can earn more elsewhere."

Tech Lead (R - Reality):
  "Tell me about the work you've been doing. What do you think
   makes the staff case?"

[Engineer lists 5 projects. Tech lead listens, asks clarifying
 questions about scope, impact, and visibility.]

Tech Lead:
  "When the promotion committee reviewed your case, what was the
   gap they named?"

Engineer:
  "They said my work hasn't had 'cross-org impact'. I don't know
   exactly what that means."

Tech Lead:
  "What have you done so far to understand what they mean?"

Engineer:
  "I read the leveling doc. Honestly, I haven't asked them directly."

Tech Lead (O - Options):
  "What could you do?"

Engineer:
  "Ask the committee what specifically they're looking for."

Tech Lead:
  "Good. What else?"

Engineer:
  "Talk to someone who was recently promoted to staff."

Tech Lead:
  "What else?"

Engineer:
  "Pick a bigger project. Maybe the platform-migration one I
   passed on because I thought it wasn't interesting."

Tech Lead:
  "What else?"

Engineer:
  [pause] "I could ask you to sponsor me more actively — coach me
   on what cross-org impact looks like, put me in rooms where I
   can earn it."

Tech Lead:
  "What else?"

Engineer:
  "I could leave. I could go get Staff somewhere else."

Tech Lead (W - Will):
  "Which of these are you going to actually do?"

Engineer:
  "I want to try for one more cycle here. I'll ask the committee
   for specifics. I'll ask you for sponsorship. And I'll take the
   platform-migration project if it's still on offer."

Tech Lead:
  "What's the first step and when?"

Engineer:
  "I'll email the committee chair tomorrow. I'll talk to you
   Friday about the project."

Tech Lead:
  "What might get in your way?"

Engineer:
  "Me getting frustrated again and deciding to bail."

Tech Lead:
  "How will you handle that?"

Engineer:
  "Maybe we check in every two weeks on how it's going. If I'm
   still stuck in 3 months, we talk about next steps honestly."

Tech Lead:
  "Deal. What's your takeaway from this conversation?"

Engineer:
  "That I've been passive about this. I've been waiting to be
   noticed rather than actively building what they're looking for."

Notice what happened: the tech lead never told the engineer what to do. They asked questions that let the engineer see their own situation more clearly. The engineer generated their own options and committed to their own plan. That plan is far more likely to be executed than one the tech lead dictated.

When It Works

1:1s with direct reports (especially developmental 1:1s)
Mentoring conversations
Career development discussions
Unblocking someone stuck on a problem
Any situation where the coachee has the capability to solve the problem but needs help structuring their thinking

When It Does Not Work

When the person genuinely lacks information — If they don't know how something works, teaching is faster than questioning. GROW is for when they have the knowledge but aren't activating it.
In crisis — If the building is on fire, give directions, not questions.
When you hold authority you cannot delegate — If you are about to make a decision affecting them, do not pretend it is their call.
When they are too emotionally overwhelmed — Questions to a deeply distressed person feel like cross-examination. Lead with care (CEDAR-style) first; coach later.
When the coach has a stake in a specific outcome — GROW requires the coach to be neutral about the answer. If you care about the outcome, you are not coaching; you are persuading.

Common Failure Modes

Structure

Skipping Goal — Jumping straight to Reality without establishing what the coachee wants. The conversation meanders.
Overstaying Reality — Letting the coachee vent for 25 minutes about the situation without moving to options. Useful to a point; useless beyond it.
Single Option — Accepting the first option that emerges as the plan. GROW's power is in generating breadth before choosing.
Abandoning Will — Ending without a specific commitment. "I'll think about it" is not Will.

Technique

Leading Questions — Questions that have an answer you want. "Don't you think you should...?" is a statement wearing a question mark.
The Advice Drop — Disguising advice as a question: "Have you considered doing X?" The coachee hears the suggestion, not the question.
Rescue Behavior — Jumping in when the coachee is stuck in silence. Silence is where insight often happens. Wait.
Premature Convergence — Rushing from Options to Will because the conversation feels long. Spend more time in Options; Will follows.

Relationship

Wearing Two Hats — Being the coachee's manager and their coach at the same time. The power imbalance muddies the coaching. Some managers can navigate this; many cannot.
Hidden Agenda — Running a GROW while secretly trying to lead the coachee to a specific conclusion. They always notice.
No Accountability — Never following up on commitments made. The Will step becomes theatrical.