apply-grow-coaching

name	apply-grow-coaching
description	Use when a manager wants to help a direct report solve a problem, develop a skill, or reach a goal through structured questioning rather than advice-giving — because telling people answers builds dependency while coaching builds self-sufficiency.

Apply GROW Coaching

Use the GROW model — Goal, Reality, Options, Will — to coach a direct report through a problem or development challenge by asking questions rather than giving answers.

Why This Is Best Practice

Adopted by: Google's Project Oxygen (2008–2018) identified coaching as the #1 behavior of effective managers across all Google manager effectiveness surveys; the GROW model originated with John Whitmore and Timothy Gallwey, was formalized in the 1980s at McKinsey, and is now the standard coaching framework taught in corporate leadership programs at Google, Microsoft, Unilever, and the International Coaching Federation (ICF); Michael Bungay Stanier's "The Coaching Habit" — built on the same principles — has sold 1M+ copies and is used in manager training at LinkedIn, Slack, and Shopify Impact: Google's Project Oxygen data showed that managers with high coaching scores had direct reports with significantly higher performance ratings, lower attrition, and higher satisfaction scores; the key causal mechanism: coaching-style managers build employee self-sufficiency, while advice-giving managers build dependency — dependency requires continuous manager involvement and collapses when the manager is unavailable; Whitmore's research documents that people are 3–4× more likely to follow through on solutions they generated themselves versus solutions given to them Why best: Advice-giving (the default manager behavior) creates the right answer in the short term but the wrong habit in the long term — the employee learns to wait for the manager's answer rather than developing their own judgment; GROW provides a repeatable four-stage structure that guides employees to their own solutions while the manager facilitates, making the manager a multiplier rather than a bottleneck

Sources: Whitmore "Coaching for Performance" (Nicholas Brealey Publishing, 5th ed. 2017); Google re:Work "Guide: Coach Your Employees" (rework.withgoogle.com); ICF "Core Competency Framework" (coachingfederation.org); Bungay Stanier "The Coaching Habit" (Box of Crayons Press, 2016)

Steps

1. Recognize the coaching moment

A coaching conversation is appropriate when:

• The employee has a problem they're stuck on but likely has the resources to solve it
• The employee is developing a skill and needs to build their own judgment, not execute your approach
• The employee is making a decision where their ownership matters to the outcome

A coaching conversation is NOT appropriate when:

• There is one correct answer the employee doesn't have (teach or direct instead)
• Speed is critical (coaching takes longer than telling in the short term)
• Safety or compliance is involved (non-negotiable standards require clear direction)

Signal the mode explicitly: "I'm going to ask you some questions rather than give you my view — I want to hear how you're thinking about this."

2. G — Goal: establish what they want from this conversation

The first step is not to understand the problem — it is to understand what outcome the employee wants from the coaching conversation itself. Without this, the conversation can wander without resolution.

Key questions:

"What would you like to get out of this conversation?"
"What would a good outcome of the next 30 minutes look like for you?"
"By the end of our time, what do you want to have clarity on or decided?"

A common goal: "I want to figure out how to handle [situation]." A vague goal: "I want to talk about [situation]." If the goal is vague, press: "When you say you want to talk about it — what specifically would feel resolved?"

The goal anchors the entire conversation. Return to it if the conversation drifts.

3. R — Reality: understand the current situation without solving it

Explore the current situation — what is happening, what they have tried, what is getting in the way — through questions only. Resist interpreting or advising.

Key questions:

"What's happening right now? Tell me the situation."
"What have you already tried?"
"What's working? What isn't?"
"What's getting in the way?"
"What haven't you tried yet that might make a difference?"
"On a scale of 1–10, how much does this problem feel within your control?"

The manager's role in the Reality phase is to help the employee see the situation more clearly — not to add their own assessment of the situation. Ask questions that prompt reflection:

"What would a neutral observer say about the situation?"
"What are you not seeing that might be important?"
"If you imagine the situation six months from now if nothing changes, what does that look like?"

4. O — Options: generate possibilities before evaluating them

Once the reality is clear, generate a range of options. The key discipline: generate before evaluating. Premature evaluation shuts down creative options.

Key questions:

"What options do you have?"
"What else could you do?"
"If there were no constraints, what would you do?"
"What would someone you respect do in this situation?"
"What haven't you considered that might be worth exploring?"

Wait until the employee has generated at least 3–5 options before asking them to evaluate. The first option is usually the most obvious one; the third or fourth is usually where insight appears.

After options are generated, ask them to evaluate:

"Of those options, which feels most promising?"
"Which would you be most willing to commit to?"
"What are the trade-offs between these options?"

The manager should not rank or recommend options during the GROW conversation. If they ask "what would you do?", a response is: "I have a view, but I want to hear yours first — which feels most right to you?"

After they have committed to an option, if the manager has an important consideration the employee hasn't raised, it can be offered: "Can I share one thing I'm thinking about that you haven't mentioned?" — not as a redirect, but as additional input.

5. W — Will: commit to specific action

The coaching conversation only changes behavior if it ends with a specific commitment. Vague intentions do not become actions.

Key questions:

"What are you going to do? And by when?"
"How committed are you to that — on a scale of 1–10?"
"What might get in the way, and how will you handle that?"
"What support do you need from me?"

If commitment is low (below 7 on the 1–10 scale), surface the obstacle before ending: "You said 6 — what's the 6 telling us?" Often this reveals either a missing option that hasn't been considered, or that the stated option is not actually what the employee wants to do.

Close by confirming the action, the timeline, and how you'll follow up:

"So you're going to [specific action] by [date]. I'll check in on [date] — 
is that right?"

6. Follow up

At the agreed follow-up, start with: "You said you were going to [action] — how did it go?" Resist filling the gap with your own assessment. Let them report first.

If they succeeded: "What made it work? What did you learn?" — reinforces the skill of solving problems independently.

If they didn't: return to Reality and Options — "What got in the way? What would you do differently?"

Rules

• Ask before telling — the default switch is from advice to questions; if you find yourself explaining and advising more than asking, you've left coaching mode
• Generate before evaluating — in the Options phase, generate at least 3–5 options before asking which to pursue; premature evaluation locks in the obvious answer
• Their solution, not yours — if your preferred answer emerges, offer it as a question: "Have you considered [option]?" not "You should do [option]"
• One question at a time — stacked questions ("What did you try and what was the result and what would you do differently?") produce fragmented answers; one question, then wait
• Silence is productive — resist filling pauses; thinking looks like silence; discomfort with silence makes managers revert to advising

Common Mistakes

• Coaching when the right answer is teaching: if the employee genuinely doesn't have the knowledge needed, GROW is the wrong tool — teach the concept first, then coach on application.
• Asking leading questions: "Wouldn't it make sense to do X?" is not coaching; it is advice framed as a question and is immediately recognized as such, which damages trust.
• Skipping the Goal stage: jumping straight into Reality without establishing what outcome the employee wants produces an unfocused conversation; the Goal anchors everything that follows.
• Stopping at Options without Will: the most common GROW failure mode is a great conversation that ends with "interesting discussion" and no concrete commitment; if there is no specific action and timeline, the coaching didn't produce change.
• Switching to advice mid-conversation: when a coaching conversation surfaces a problem the manager wants to solve, the pull to give advice is strong; name it: "I have a strong instinct to give you my answer — but I want to hear yours first."

When NOT to Use

• When the employee needs a decision made, not helped: some situations require the manager to make a call; coaching when someone needs a decision frustrates them and wastes time.
• When there is a clear compliance or safety issue with one correct answer: coaching implies that the employee's answer is as valid as any other; for non-negotiable standards, teach and direct.
• When the employee is in acute distress: a coaching conversation requires cognitive bandwidth to explore and generate; a person in crisis needs acknowledgment and support first; coaching comes after stabilization.
• For experienced employees on tasks they have mastered: D4 employees on familiar work don't benefit from GROW questioning; they need clear outcomes and autonomy (S4 delegation); coaching is for developing judgment, not for people who already have it.