Coaching: Give Fewer Answers, Make More Thinking Space
Topic: Coaching·4 principles
"Coaching is unlocking a person's potential to maximize their own performance." — John Whitmore
This week's premise: As a manager who came up through engineering, your biggest instinctive trap is "I know the answer, let me just tell you." As an IC that was your edge; as a manager it's your ceiling — the more answers you hand out, the less your reports think for themselves, and the more they can't function without you. Coaching isn't passivity, nor pretending you don't know; it's a deliberate restraint: swap "telling" for "asking," and "solving it for them" for "helping them solve it." The cost is speed — your first coaching conversation takes three times as long as just giving the answer. The payoff compounds — three months later they stop bringing you the same class of problem. Four principles this week: structure a coaching conversation with GROW, tame your "advice monster," seven power questions that change the conversation, and the most honest lesson — when NOT to coach, when telling them directly is the responsible move.
PRINCIPLE 01
GROW: The Four Gears of a Coaching Conversation
Goal, Reality, Options, Will
GROWstructureframework
Principle in one line
A coaching conversation isn't a ramble. Move through Goal → Reality → Options → Will, and let the report walk themselves to a conclusion inside your questions — you drive the gears, not the content.
In their words
"Coaching is unlocking a person's potential to maximize their own performance. It is helping them to learn rather than teaching them."— John Whitmore, Coaching for Performance, Ch.1
The four GROW gears
Scene
Situation: a senior engineer walks into your 1:1 and says, "I think we should rewrite this service in Rust."
✗ IC instinct (snap judgment)
"A rewrite isn't worth it right now — we don't have the bandwidth and nobody knows Rust. Fix the existing bugs first." You may be right, but he'll keep bringing you half-baked ideas; he never learned to evaluate it himself, and you missed his real concern.
✓ Run GROW
G: "Step back — what's the real problem you want the rewrite to solve? Performance, maintainability, something else?"
R: "Where exactly is the service stuck today? What data do you have — latency, incident rate, slow to change?"
O: "Besides a full rewrite, what other ways could solve that problem? … And what else?" (forcing out option two and three: rewrite the hot module, add caching, profile and optimize)
W: "Of these, which would you be willing to validate over a week? What do you need me to unblock?"
Checklist: before you open GROW
Is this actually a topic worth coaching? (not a crisis, not pure missing info — see Card 4)
Can I hold back and offer zero solutions until the Options stage?
Is the Goal his goal, not one I set for him?
In Reality, am I asking for facts or quietly hinting at my own verdict?
Does the end land on a concrete next step + a time?
Common mistakes
Skipping G straight to O. Discuss solutions before aligning on the goal and you spend an hour solving the wrong problem.
Reality turns into interrogation. "Why didn't you raise this earlier?" — one accusation and the door slams shut.
Fake GROW. The questions are just wrapping; you had the answer all along and wait for him to "guess right." Reports can smell it — worse for trust than just telling them.
No Will. A great chat with no commitment; same thing comes back next week unchanged.
Key references
John Whitmore, Coaching for Performance (the foundational treatment of GROW; traceable back to Timothy Gallwey's The Inner Game of Tennis). Timothy Gallwey, The Inner Game of Tennis — "the opponent is in your own head," the psychological starting point of coaching.
PRINCIPLE 02
Asking vs Telling: Tame Your Advice Monster
Tame the Advice Monster
questionsrestraintdirective spectrum
Principle in one line
There's an "advice monster" in your head that wants to leap out with a solution before your report finishes talking. Stay curious a little longer; rush to action and advice a little more slowly.
In their words
"Stay curious a little longer, and rush to action and advice-giving a little more slowly."— Michael Bungay Stanier, The Coaching Habit, Introduction
The advice monster's three faces
Tell-it: "Let me tell you what to do" — the one you know best, the engineering leader's default.
Save-it: "Don't worry, I'll handle it" — taking the monkey back onto your own shoulder (see Day 13).
Control-it: "No, it has to be my way" — fear of losing control, so you reclaim the autonomy.
Every time you want to blurt out the answer, ask yourself first: which monster just jumped out?
Scene: hand the ball back
Situation: a mid-level engineer asks, "How should I design this API? Cursor pagination or offset?"
✗ Hand over the answer
"Use cursor — offset has performance problems on large datasets." Solved in three seconds, but what he learns is "bring design questions to BigCat," not "how to weigh it myself."
✓ Return the judgment first
"Which way are you leaning right now? Walk me through your reasoning." (make him expose his thinking)
(after he answers) "And in what scenario would that choice break down?" (push him to find the edges himself)
"If the data grows to 10 million rows, does your call change?" — most of the time he arrives at cursor himself, and remembers why. When he's truly stuck or time is tight, then give it directly — but that's Card 4's judgment call.
Checklist: micro-habits of restraint
After my report finishes, did I ask one question before deciding whether to give a solution?
Am I giving "an answer," or "a question that keeps them thinking"?
When I'm especially sure I'm right — is that exactly the moment to hold back?
This week, what's my rough ratio of "asking : telling"?
Common mistakes
Fake questions. "Don't you think we should use cursor?" — that's a command dressed as a question; all he hears is the command.
Never giving answers = a different dereliction. Restraint isn't dogma. Withholding info he genuinely needs is torture, not coaching.
Using coaching to dodge hard talks. When you should say "this wasn't good enough," hiding in "what do you think?" — feedback is not a substitute for coaching (see Day 2).
Female Leader's Note
Female Leader's Note
Coaching naturally leans on questions and holds back on verdicts, which more easily triggers the double bind for women leaders: asking gets read as "she can't make up her mind," while giving a direct answer gets read as "abrasive." One counter is to name the intent explicitly: "I'm deliberately not handing you a solution yet — I want to hear how you weigh it, to help you build judgment, not because I have no view." Spelling out the restraint turns it from "weakness" into "a deliberate leadership move," instead of letting the other party default to assuming you have no opinion.
Key references
Michael Bungay Stanier, The Coaching Habit (source of the advice monster's three faces). Myles Downey, Effective Coaching — the directive ↔ non-directive spectrum, from "telling" to "pure listening": giving the answer is just the leftmost notch.
PRINCIPLE 03
Seven Power Questions: Replace Your Question Bank
Seven Questions That Change The Conversation
questionsscriptstoolkit
Principle in one line
A good coach relies not on good answers but on a few good questions you can reuse. Memorize them, so that in the conversation you don't slip back into "let me tell you."
In their words
"'And what else?' — the best coaching question in the world. The first answer is almost never the only answer, and rarely the best answer."— Michael Bungay Stanier, The Coaching Habit, Ch.3
Seven questions (drop straight into your next 1:1)
Kickstart
"What's on your mind?" Ten times the signal of "how's the project," opens straight to the real issue.
AWE
"And what else?" Ask it 2–3 times. The first answer is a reflex; the gold is in the third layer.
Focus
"What's the real challenge here for you?" The "for you" forces him from abstract complaint down to himself.
Foundation
"What do you want?" Asked directly — often nobody has ever asked him.
Lazy
"How can I help?" Forces him to make an explicit request, instead of you guessing where to intervene.
Strategic
"If you say yes to this, what are you saying no to?" Surfaces the trade-off.
Learning
"What was most useful for you today?" Lets him extract the takeaway himself — it sticks better.
Silence is part of the question — the 8-second rule
After a real question, count to 8 before you speak. Most people start adding at 4 seconds, but the real thinking happens at seconds 5–8. Rushing to fill the silence is thinking for them — you'll only get the surface answer.
✓ Physical move
Ask, then pick up your water, take a slow sip, set it down. Eight seconds pass and you still haven't spoken — and he'll start saying the real layer.
Checklist: question design for this conversation
How many of my prepared questions are yes/no? Cut them, make them open-ended.
Did I use one "And what else?"
After asking, how many seconds of silence did I hold?
At the end, did I let him say the "most useful point" himself?
Common mistakes
Chains of "why." "Why? Why?" makes people defensive. Ask more "what / how," less "why."
Asking then answering yourself. "What do you think? Is it because the timeline's too tight? I think so too…" — you just stole his answer.
Reading the seven as a script. They're tools, not a flow; pick by where the conversation actually goes.
Key references
Michael Bungay Stanier, The Coaching Habit (full source of the seven core questions: Kickstart / AWE / Focus / Foundation / Lazy / Strategic / Learning). Kim Scott, Radical Candor — "What could I do or stop doing that would make it easier to work with me?" belongs to the same power-question family.
PRINCIPLE 04
When NOT to Coach: Telling Is Sometimes the Job
When Telling Is the Responsible Move
boundaryjudgmenthonesty
Principle in one line
Coaching isn't universal. When the situation is urgent, when safety or compliance is at stake, or when the report genuinely lacks the information to judge — don't ask, give a clear instruction. Hiding in "what do you think?" when you should be telling is dressing up an abdication of responsibility as empowerment.
In their words
"Sometimes the answer is to tell people what to do. The skill is knowing which mode you're in — and being honest about it."— adapted from Camille Fournier, The Manager's Path, Ch.3
Coach or Tell? Two dimensions
Scene
Situation: a live P1 incident, DB connection pool saturated, the report posts in the incident channel: "Should we discuss a few recovery options?"
✗ Misplaced coaching
"What options do you see? What are the trade-offs of each?" — this is not coaching time. Every extra question is another minute of user impact.
✓ Command now, coach later
During: "First raise the pool cap to X, restart service B, I'll notify stakeholders. Once we're stable for 30 minutes we'll look at root cause." — clear, single chain of command.
In the postmortem: "Now let's coach — if next time it's only you, how would you decide between scaling first or restarting first?" Move the coaching to the right time.
Checklist: pick the mode before you speak
Is there time for him to think it through? (incident, deadline day = no)
Does he have the information and experience to make a sound call? (brand-new domain = give material first)
Is the cost of being wrong reversible? Reversible = let him try; irreversible and high-risk = give direction.
Did I tell him which mode we're in? ("I'm giving you the answer this time, because…")
Common mistakes
Treating coaching as a default creed. Read one book and you question everyone on everything; a new hire feels you're stonewalling, refusing to teach.
Silently switching modes. You coach usually, then suddenly command in an incident — the report is bewildered. Tell them up front: "in emergencies I'll direct."
Only ever telling. The other extreme — answering everything, the team never grows judgment, and you firefight forever.
Key references
Camille Fournier, The Manager's Path (Ch.3, switching between coaching and direct management). Ken Blanchard, Situational Leadership II — the classic frame for switching among Directing / Coaching / Supporting / Delegating by the report's "competence × commitment."
This Week's Exercise · Your Day 14 Action
Do one concrete thing this week — not reflection, not reading:
Catch the next moment a report comes to you "for the answer" ("how should I handle this?"). First use Card 4's checklist to judge: should I coach right now? If yes — resist giving the answer and ask three questions instead: "Which way are you leaning?" → "Any other approaches?" → "Which would you try first?" After each one, count to 8 before speaking.
Afterward, write two lines: (1) how far the conclusion he reached was from the answer in your head; (2) the moment you most wanted to jump in with the answer. That moment is your advice monster — recognize it next time.
Going Deeper
Does coaching fail to translate in high-power-distance / East Asian teams?
It can, but it's adjustable, not unusable. In high-power-distance cultures, when a senior report asks "what should I do," they may genuinely expect the authority to give direction; your "what do you think?" can be read as a test, a dodge, or even "he doesn't know either." The counter isn't to abandon coaching but to name it explicitly: "I'm asking not to withhold the answer but to hear your judgment and help you build this muscle — if you can't land it, I'll make the call." Spell out the good intent behind the question and add a clear fallback commitment, and coaching won't be misread as abdication. Culture doesn't change the framework — it changes the packaging and the setup.
Doesn't a structured conversation like GROW feel too formulaic, too mechanical?
It does early on, and you should accept the clumsiness — like memorizing the gear sequence when you learn to drive. GROW is scaffolding; its purpose is to hold you up at the exact moment you most want to leap in with the answer. Once fluent, the four gears internalize into instinct — you stop "reading a script" and naturally align on the goal, then probe reality. The real risk isn't the formulaic feel; it's fake GROW: you had the answer all along and use questions to lead them to guess it. That hurts trust more than just telling them, because they can smell being manipulated. The structure can be mechanical; the intent cannot be fake.
If the report isn't capable enough yet, is hard-coaching wasting both your time?
Yes — and that's the heart of Card 4. Coaching presupposes the other person can reach a reasonable answer themselves; you just help them get there faster and more consciously. If they're in a brand-new domain and don't even know the option space, asking "what other approaches?" yields only blankness or wild guesses. The right move then is to tell / teach first: give material, examples, a starting point, and once they have basic judgment, switch back to coaching. Use coaching on the mid-to-late part of the capability curve; the early part is teaching — both are right, the error is mixing them up.
As a big-company tech lead manager, how does coaching's time cost ever pay off?
In the short term it doesn't; in the long term it's the only thing that does. Giving the answer solves one instance in three minutes, but what you buy is "he comes back to ask again" — problem volume grows linearly with team size and eventually drowns you. Coaching costs 3x the first time, but buys him solving the same class of problem himself next time, and your intervention rate falls over time. It's the same ledger as Day 13's delegation: the prerequisite for the next level up is scaling out judgment that doesn't depend on you, and judgment only grows from him making decisions, not from you feeding answers. Treat coaching as an investment in the team's judgment, not the per-incident cost of one solution.
Coaching, mentoring, feedback, therapy — where are the boundaries, and how not to cross them?
These four get conflated constantly. Coaching: you don't give the answer, you help them find their own (this issue). Mentoring: you give advice and a path from your own experience ("here's how I did it back then"). Feedback: you tell them a fact about their performance and its impact (Day 2) — that's not asked out of them, it's something you have to say. Therapy: handling psychological trauma or clinical issues — beyond the manager role; refer to professional resources. The most common boundary slip is using coaching to dodge feedback: hiding in "what do you think?" when you should plainly say "this wasn't good enough." Remember: coaching helps them think, feedback is what you must say — don't substitute the former for the latter.