The Coaching Habit
Michael Bungay Stanier's pitch that most managers have an "advice monster" problem, and a short list of deceptively simple questions designed to starve it, a little at a time, in conversations that already happen every day.
Find this on the mind-map
Introduction
Stanier's starting observation is that most managers default to giving advice, fast, whether or not anyone actually asked for it. This habit feels helpful, but over time it trains a team to stop thinking for themselves and start bringing you their problems instead of their solutions. The book's whole approach is built around a small set of questions, used in the ordinary moments management already happens, rather than a program you have to schedule separately.
The Advice Monster
Stanier's name for the reflex that kicks in the second someone describes a problem: the urge to jump in with a fix. It's not really about ego, though it can be. It's that giving advice feels fast, competent, and immediately useful, while asking a question feels slower and less obviously helpful in the moment. The habit the whole book is building is simply: notice the Advice Monster showing up, and ask one more question before you let it talk.
The Kickstart Question: "What's on your mind?"
An open, un-leading way to start a conversation, instead of a status-update prompt like "how's it going?" that invites a shallow answer. It signals that you're ready to talk about whatever actually matters to the other person right now, not whatever you assumed would be on the agenda.
The AWE Question: "And What Else?"
Stanier calls this the best coaching question in the world, and the whole book could arguably be built around it alone. The first answer someone gives to a hard question is rarely their only answer, and often not their best one. "And what else?" buys more of their actual thinking before you jump to solving anything, and it costs you nothing to ask it two or three times in a row.
The Focus Question: "What's the Real Challenge Here for You?"
People often bring you the first problem they noticed, not the real one underneath it. This question pushes past the presenting issue toward the thing actually worth solving. And the "for you" matters, because it keeps the question personal instead of abstract, which is usually where the honest answer lives.
The Foundation Question: "What Do You Want?"
Deceptively blunt, and often skipped because it feels almost too simple to ask out loud. A lot of stuck conversations are stuck because nobody has actually said what they want, specifically. People talk around it, assuming it's obvious, and it usually isn't.
Manager A spends twenty minutes helping a direct report work through a frustrating project update. Manager B asks, two minutes in, "what do you actually want out of this conversation?" and finds out the direct report wanted validation, not a solution. B's conversation is shorter and actually lands.
The Lazy Question: "How Can I Help?"
Asked instead of assuming what kind of help is wanted. It forces the other person to be specific about the ask, which often reveals they didn't need you to do anything at all, just to listen, or to remove one specific obstacle you'd never have guessed.
The Strategic and Learning Questions
The Strategic Question, "if you're saying yes to this, what are you saying no to?", makes the hidden cost of a new commitment visible before it's made. The Learning Question, "what was most useful for you?", closes a conversation by making the other person name their own takeaway, instead of you summarizing it for them, which is both more memorable and a small but real transfer of ownership back to them.
Putting It Together
None of these questions is complicated on its own; the discipline is using them instead of the advice that wants to come out first. Stanier's real claim is that a manager who asks one more question before giving one more answer, consistently, over months, ends up with a team that solves more of its own problems. Not because the questions are magic, but because advice given fast trains dependence, and a good question, asked at the right moment, trains capability instead.

Why It Matters for Leaders
The habit this book is actually trying to build isn't a script of seven questions, it's a half-second pause between hearing a problem and offering a fix. Most managers skip that pause because answering fast feels like the job. The cost shows up slowly: a team that brings you problems instead of solutions, because you've spent months proving you'll solve them faster than they will.
The AWE question, "and what else?", is the one with the most leverage for the least effort, because it costs nothing and almost always surfaces something better than the first answer. Most coaching conversations end on the first thing someone says, which is usually the most obvious thing, not the most useful one. Asking twice more isn't a technique, it's just refusing to settle for the first draft of someone's thinking.
The harder shift is giving up the satisfaction of being the one with the answer. A manager who's good at this starts noticing that their 1:1s get shorter, not longer, because the direct report arrives at their own answer faster than the manager could have handed them one. That's the actual payoff: less of your time spent solving, more of the team's capability built.
Picture a manager, Noah, whose direct report comes to him visibly frustrated about a stalled project. Noah's instinct is to immediately suggest three fixes. Instead he asks, "what's on your mind?", then, after the answer, "and what else?" The direct report's third answer, the one Noah never would have gotten to with his own first instinct, is the actual problem: he doesn't trust that another team will deliver their part on time, and he's never said so out loud. Noah didn't solve anything. The direct report did, in about four minutes.
What to do next
Reinforce your understanding of The Coaching Habit
Books related to The Coaching Habit
Coaching for Performance
Sir John Whitmore's foundational case for coaching-style management over command-and-control, built on a single idea: performance is limited less by skill than by interference, and a manager's job is to remove the interference, not supply the answer.
Elevate
Robert Glazer's case, from his book "Elevate: Push Beyond Your Limits and Unlock Success in Yourself and Others," that performance isn't a willpower problem. It's a capacity problem across four specific domains, built like a muscle, not willed into existence overnight.
First, Break All The Rules
A large-scale look at what the best managers actually do differently, and the uncomfortable finding that most of it runs against conventional management wisdom, starting with the idea that you shouldn't try to fix people's weaknesses.
Multipliers
Liz Wiseman's case that the biggest lever on a team's output isn't headcount or talent density, it's whether the leader in the room makes people smarter or slowly makes them smaller.
Team Topologies
Skelton and Pais's case that most team structures are drawn to fit an org chart, not the actual flow of work, and a small set of team shapes and interaction rules for fixing that, built around a resource every leader habitually overspends: people's cognitive load.
The First-Time Manager
The unglamorous, practical handbook for the specific week your job title changed and nothing else came with instructions. Less a framework, more a set of answers to the questions new managers are usually too embarrassed to ask out loud.
The Five Dysfunctions of a Team
Patrick Lencioni's pyramid of the five behaviors that sink teams without much notice, stacked so that each one is actually caused by the dysfunction beneath it, which means fixing results or accountability first almost never works.
The Making of a Manager
Julie Zhuo's field notes from becoming a manager in her twenties with no idea what the job actually was. A clear-eyed answer to the question most new managers are too embarrassed to ask out loud: what am I actually supposed to be doing all day?
The Manager's Path
Camille Fournier's map of the actual career ladder from doing the work to leading an organization of leaders, written for engineering managers, but mostly a clear-eyed account of how the job itself changes at every rung, which almost nobody explains to you before you climb it.
Turn the Ship Around!
A submarine captain's account of giving up the one thing every leader is taught to protect, being the person who gives the orders, and turning the worst-performing submarine in the fleet into one of the best by making every sailor think like a captain instead.
Skills related to The Coaching Habit
Frameworks related to The Coaching Habit
Dunning-Kruger Effect
Knowing little makes you feel unstoppable; knowing more makes you hesitate — the loudest voice is rarely the most reliable one.
Goldilocks Principle
Support runs on a dial between micromanagement and abdication — enough direction for clarity, enough space for ownership, always moving.
Hawthorne Effect
People change how they behave when they know they're watched — your attention is an intervention that changes what you see.
Maslow's Hierarchy of Needs
Abraham Maslow's five-level model of motivation, applied to leadership as a stack — mastery, trust, belonging, up through recognition and vision.
McKinsey 9-Box Model
A 3x3 grid that plots each person on performance against potential, giving nine distinct calls instead of one blurry verdict.
Multipliers and Diminishers
Liz Wiseman's split between leaders who bring out best thinking in people around them, and those who shut it down.
Situational Leadership
There's no right way to lead — only the right way for this person right now: direct, coach, support, or delegate.
The 6 Human Needs
Every behavior at work is really an unmet need in disguise — six needs, popularized by Tony Robbins, worth checking first.
The Architecture of High-Performing Teams
Six elements, built like a temple — culture as the base, four pillars, vision as the roof — name the missing piece.
The Bannister Effect
One person breaking a barrier makes it stop being fixed for everyone else — break the unspoken belief in public first.
The Five Dysfunctions of a Team
Lencioni's pyramid of five team-killing behaviors — a lack of trust at the base drags everything above it down.
The Inner Drive
A leadership take on Daniel Pink's *Drive* that turns three conditions for motivation — autonomy, mastery, purpose — into habits for 1:1s.
The Pygmalion Effect
What you expect from someone leaks into how you treat them, which shapes what they become — for better or worse.
The Thomas-Kilmann (TKI) Model
Five conflict styles, two dials — how hard you push, how much room you give — chosen on purpose, not by default.
Tuckman's Stages of Team Development
Every team moves through five predictable stages — forming, storming, norming, performing, adjourning — each demanding a different move from you.