The Coaching Habit: Say Less, Ask More & Change the Way You Lead Forever

1. 1Open with the Kickstart Question — 'What's on your mind?' — to grant autonomy: you show trust and let them choose the topic instead of guiding, telling, or diagnosing.
2. 2Ask exactly one question, then go quiet and wait for the answer; resist filling the silence with your own answer.
3. 3Reframe every impulse to ask 'Why?' into a 'What' question — replace 'Why did you do that?' with 'What were you hoping for here?' — so people build solutions instead of getting defensive.
4. 4Slow the rush to fix by asking the Focus Question — 'What's the real challenge here for you?' — so they own the problem definition rather than accepting the first problem you'd solve for them.
5. 5Use 'And what else?' to draw out more and better options, so the decision and its ownership stay with them.
6. 6Raise the TERA Quotient deliberately: signal tribe (I'm with you), set expectation (make the next step clear), protect rank (don't diminish status), and preserve autonomy (give them a say) — asking rather than telling does all four.
7. 7Close with the Learning Question — 'What was most useful for you about this conversation?' — which forces them to extract and name their own value, reinforcing that the wisdom was theirs.

A team member drops a problem on your desk and every fibre twitches to solve it. Instead of jumping in, you ask 'What's on your mind?' and let them talk. When they describe a symptom, you resist the Advice Monster and ask 'What's the real challenge here for you?' — adding 'for you' so they locate their own answer faster and more accurately. Rather than 'Why did you try that?' (which lands as 'What the hell were you thinking?'), you ask 'What made you choose this course of action?' You then ask 'And what else?' until they surface more options, because at least one more option nearly halves the failure rate. You never take over, so they stay self-sufficient and you avoid becoming the VP of Bottlenecking. You end with 'What was most useful for you about this conversation?' — they extract their own learning and leave having created their own wisdom.

• If you're tempted to begin a question with 'Why', then reframe it to start with 'What' — you're not trying to fix, so you don't need the backstory.
• If you catch yourself about to give advice, then ask one more question first — your advice is not as good as you think it is, and telling robs them of ownership.
• If the first problem on the table feels fixable, then ask 'What's the real challenge here for you?' — the first problem is usually a symptom, not the real one.
• If you want their genuine choice, then keep the question open-but-focused (like 'What's on your mind?') so you grant autonomy without inviting everything.
• If you want to lift engagement in the moment, then ask rather than dictate — it raises tribe and autonomy in the TERA Quotient.

• Asking 'Why?' in a focused conversation — the tell: their tone shifts defensive and you're suddenly gathering backstory to fix the problem yourself.
• Letting the Advice Monster hijack the moment — the tell: within seconds (doctors interrupt at eighteen) you're offering solutions instead of a question.
• Solving the first problem presented — the tell: you feel the satisfying sense of progress, but you're 'in the wrong hole' digging faster on a symptom.
• Asking 'Was this useful?' instead of 'What was most useful?' — the tell: you get a Yes/No judgment, not the insight that embeds their own learning.
• Continuing to be the answer-source — the tell: the more you help, the more they need help, and you become the bottleneck while overdependence deepens.

• ▸Kickstart: 'What's on your mind?' — open the conversation, then stay silent
• ▸Trigger to reframe: note the moment you're tempted to ask 'Why'
• ▸'What' replacement: write the 'What...' version of that question here
• ▸Focus: 'What's the real challenge here for you?' — find the real, owned problem
• ▸'And what else?': track each additional option they generate
• ▸TERA check: which of tribe/expectation/rank/autonomy am I raising right now?
• ▸One-question rule: confirm I asked one question and waited
• ▸Learning close: 'What was most useful for you about this conversation?' — capture their words
• ▸My share (optional): what I found most useful, to strengthen the social contract

1. 1Recognize the baseline: five times a second, at an unconscious level, the brain scans 'Is it safe here or dangerous?' Your job in every interaction is to raise the reading toward safe, because a safe brain thinks at its most sophisticated level and handles ambiguity better.
2. 2Run the interaction through the four TERA drivers before and during it: Tribe ('Are you with me or against me?'), Expectation ('Do I know the future or not?'), Rank ('Are you more or less important than I am?'), Autonomy ('Do I get a say or not?').
3. 3Raise Tribe by asking questions rather than telling — asking signals you're on their side. 'What do you want?' specifically increases the sense of tribe.
4. 4Raise Expectation by making what happens next clear: signal the shape of the conversation, cut the intro and ask the question directly (as the Bond-opening masterclass notes, no fumbling setup).
5. 5Protect Rank by not diminishing status: don't jump to the advice-giver/fix-it mode, which implicitly says you're more important. Ask more, tell less.
6. 6Raise Autonomy by giving a genuine say: use 'What do you want?' and 'And what else?' so the person generates options and choices rather than receiving your imposed course of action.
7. 7Answer the same question for yourself and share it. Asking 'What do you want?' and also stating what you want makes it an adult-to-adult exchange of value, which strengthens tribe and rank simultaneously.

You're stuck with a team member and you're pretty sure you know what they want but haven't asked — the classic 'instead of' trap. Instead of imposing your course of action (which lowers their Autonomy and, by fixing it for them, lowers their Rank), you ask 'What do you want?' This is direct rather than indirect, so Expectation stays high — they know exactly what's being asked. Because you're asking rather than telling, their brain reads you as on-side, raising Tribe. For bonus points you then tell them what you want too, turning it into an exchange of value and an adult-to-adult conversation. All four TERA levers move up at once, so both of you stay at your smartest rather than dropping into fight-or-flight.

• If you think you already know what they want, then stop and actually ask 'What do you want?' — the first assumption is almost never the best answer.
• If the situation feels tense or high-stakes, then cut the intro and ask the question plainly to keep Expectation high rather than adding preamble that muddies what's coming.
• If you catch yourself in advice-giver/fix-it mode, then convert the statement into a question — telling lowers their Rank and Autonomy.
• If a person gives you one answer, then ask 'And what else?' to restore Autonomy and generate better options (binary choices fail more than 50% of the time; one extra option cuts failure to ~30%).
• If you want to strengthen tribe and rank at once, then answer 'What do you want?' for yourself and share it, making it a mutual exchange.

• Assuming you know what they want and skipping the question — the tell is you're proposing solutions before anyone has stated the outcome.
• Padding the question with a long intro — the tell is the other person looks braced or uncertain; you've lowered Expectation by hiding what you're actually asking.
• Slipping into the Advice Monster / expert-fix-it mode — the tell is your organization's premium on answers plus your own anxiety pulling you to give advice; it silently lowers their Rank and Autonomy.
• Imposing a course of action to feel decisive — the tell is you framing choices as binary ('should we or shouldn't we?') instead of generating options, which drops Autonomy and raises failure rates.
• Treating TERA as a one-time check rather than a live reading — the tell is the conversation cooling after you subtly diminished someone's status mid-interaction, since rank is played out in the moment, not by title.

• ▸Situation & person: name the specific interaction (be specific, e.g. 'when Jenny asks for feedback in the team meeting').
• ▸Tribe move: one thing you'll do to signal you're on their side (usually: ask, don't tell).
• ▸Expectation move: how you'll make what happens next clear (cut the intro, name the question).
• ▸Rank check: what you might do that diminishes their status — and how you'll avoid it.
• ▸Autonomy move: the question that gives them a genuine say ('What do you want?' / 'And what else?').
• ▸What I want: your own answer to the question, ready to share as an exchange of value.
• ▸Advice Monster trigger: the moment you're most likely to jump in and fix it.
• ▸Post-check: did the reading move toward reward or risk, and what tipped it?

1. 1End every coaching conversation with the Learning Question: 'What was most useful for you?' Ask it as a distinct closing move, not an afterthought crammed into goodbyes.
2. 2Stay silent after asking. The other person needs the space to recall and reflect — this is where the second loop of double-loop learning happens and new neural pathways form. Resist filling the pause.
3. 3Force generation, not reception. Do not summarize the session's value for them ('I think what you got was...'). The retention gain comes from them generating the answer themselves; the moment you supply it, you cut the hippocampus out of the loop.
4. 4Listen for the specific insight they name, then acknowledge it (call-and-response) so it registers as real and worth keeping.
5. 5Ask 'What was most useful for YOU' rather than 'Was this useful?' — the second is a yes/no rhetorical trap; the first requires them to isolate and articulate one concrete takeaway.
6. 6Use it in both directions: ask it after conversations you lead and after conversations where you were coached, so you personally extract and encode a takeaway too.
7. 7Space the reflection. Because retention decays fast (a week later even critical insights are 'faint and distant echoes'), plan a later touchpoint that revisits the named takeaway rather than assuming one recall fixes it.

You've spent ten minutes coaching a report through a stuck project. Instead of closing with your own recap — 'So the key thing here is to talk to Jenny first' — you ask, 'What was most useful for you in this conversation?' You go quiet. She pauses, then says, 'Honestly, realizing I've been waiting for permission I don't actually need.' That sentence is generation in action: she pulled back into the second loop and made her own connection, rather than absorbing yours. Because she generated it, per the AGES model's G, her memory retention of that insight rises substantially over you having simply told her. You acknowledge it — 'That's a real one' — which lands it as call-and-response rather than letting it evaporate. She leaves with an insight she owns, and next time she needs you less.

• If you're about to summarize what they learned, stop — ask them to name it instead; their generated answer encodes, yours doesn't.
• If the conversation was one where you gave advice, ask the Learning Question anyway to convert delivered advice into a takeaway they've re-generated in their own words.
• If they answer with a vague pleasantry ('it was all great'), ask again for the single most useful thing — one specific takeaway beats a generous but empty one.
• If you feel the pull to speak into the post-question silence, wait; the reflection they do in that gap is the mechanism, not the delay.
• If the insight matters long-term, schedule a spaced follow-up — one recall won't beat the fast decay curve.

• Answering your own question — telling them the value instead of extracting it. Tell: you're doing the talking at the moment retention depends on them talking.
• Treating training/coaching as delivery and assuming absorption. Tell: material 'washed through and over' people; a week later nothing sticks because there was no generation step.
• Asking a yes/no version ('Did you find that helpful?'). Tell: you get a nod, not a named takeaway, so nothing gets encoded.
• Skipping the question to save time in a busy day. Tell: sessions end on logistics or goodbyes; no one leaves able to state what they got.
• Rushing past silence. Tell: you rephrase or add a suggestion within two seconds, collapsing the reflection window where the second loop opens.

• ▸Conversation held with: (name / topic in one line)
• ▸The closing question I asked verbatim: (target: 'What was most useful for you?')
• ▸Their generated takeaway, in their words: (write exactly what they said)
• ▸How I acknowledged it: (the call-and-response phrase you used)
• ▸What I did NOT supply: (note the summary you resisted giving)
• ▸My own takeaway from this conversation: (generate one for yourself too)
• ▸Silence held?: (yes/no — did you wait without filling the gap)
• ▸Spaced follow-up date: (when you'll revisit this takeaway to beat decay)

1. 1Open with "What's on your mind?" to let the person surface what matters most, rather than doing small talk or moving into advice mode.
2. 2When they name a challenge, resist the twitch to fix it — remember that the first problem stated is rarely the real problem (often a symptom, a ghost, or a half-baked solution).
3. 3Ask the Focus Question: "What's the real challenge here for you?" Note the two moves built in — "real" implies the surface answer isn't the actual issue; "for you" grounds it in the person and shifts them from observer to owner.
4. 4When they list many problems (Proliferation), don't pick one for them; ask "If you had to pick one of these to focus on, which one here would be the real challenge for you?"
5. 5When they talk in abstractions and generalizations ("us," "we," no "I"), ground it: "I have a sense of the overall challenge. What's the real challenge here for you?"
6. 6Sit with the pause after asking — the heartbeat of silence where they think and figure out their own answer is the point; don't rescue it by supplying the answer.
7. 7Distinguish when to coach and when to just answer: if someone asks where the folder is, tell them; don't interrogate trivial requests.
8. 8Close with "What was most useful here for you?" to make the person's own thinking visible and reinforce that they, not you, produced the resolution.

A team member says, "What's on your mind?" and answers with a long, unbroken stream: the budget for Project Tropic Thunder, then a colleague issue, then the engine making a "tock tock tock" sound on the drive in — didgeridoo-style circular breathing of problems. Each item gives you an uptick of anxiety and a pull to start advising on the one you feel most confident about. Instead of picking, you ask, "If you had to pick one of these to focus on, which one here would be the real challenge for you?" That forces them to choose and to own the priority rather than handing you a pile to solve. In another case, someone opens with "John — he's a nightmare, Shiny Object Syndrome, like working with confetti," which is Coaching the Ghost: the challenge is pinned on an absent person. You bring it back with "What's the real challenge here for you?" so the work stays with the person in front of you, not the ghost.

• If the person is describing a symptom, a secondary issue, or a half-baked solution, then ask "What's the real challenge here for you?" before offering anything.
• If they list many challenges, then have them pick one themselves rather than you selecting the starting point.
• If the conversation is all "us/we" with no "me/I," then ground it back to the person: add "for you" to re-anchor it.
• If it's a genuinely trivial factual request (where's the folder?), then just answer — don't coach.
• If you want the conversation to build capability, not just fix the fire, then append "for you" to as many questions as possible to tilt from performance toward development.

• Solving the wrong problem: you build a brilliant fix for the first thing mentioned, which was never the actual issue — the tell is you skip straight from their opening line to a solution.
• Solving the problem yourself: the team has trained you to answer, so they bring every problem to you — the tell is you feel overwhelmed doing your own job plus theirs (the therapist mutters "co-dependent").
• Becoming the bottleneck (VP of Bottlenecking): you can't answer, so you ignore the email or make a vague promise — the tell is work stalls and everyone waits on you.
• Advice Monster hijack: you intend to stay curious but leap in with suggestions — the tell is your mind turns toward finding The Answer the moment you hear the presenting challenge.
• Rescuing the silence: you ask the Focus Question then fill the pause yourself because you feel anxious ("they'll see through this") — the tell is you never let the person actually think.

• ▸Opening prompt used: record whether you asked "What's on your mind?" or defaulted to small talk/advice
• ▸First problem stated: write the surface challenge exactly as they said it
• ▸Symptom check: note whether this looks like a symptom, ghost, or half-baked solution
• ▸Focus Question asked: "What's the real challenge here for you?" — yes/no and their response
• ▸Which pattern showed up: Proliferation / Coaching the Ghost / Abstractions — circle one
• ▸Grounding move: how you re-anchored it to "me/I" and "for you"
• ▸Silence held: did you pause and let them think, or jump in? note it
• ▸Who owns the next action: name the person doing the work (should not be you by default)
• ▸Closing learning question: capture their answer to "What was most useful here for you?"

1. 1Diagnose which of the three vicious circles is draining you right now: overdependence (people rely on you excessively), overwhelm (quantity of work outpaces you), or disconnection (work has no real purpose). Name it before acting.
2. 2When a request or task lands, run it through a single filter: does this have real impact and meaning, or is it work with no purpose? Route your time, energy and resources only to challenges that make a difference.
3. 3Practice saying-no to the low-impact by giving less advice and asking more questions—the AWE Question ('And what else?') surfaces the actual issue so you stop solving the wrong, low-value problem.
4. 4Use the Focus Question and Foundation Question to get to the heart of the challenge, so your attention lands on what really matters rather than the first thing presented.
5. 5Stop being the bottleneck: use the Strategic Question to save hours for those you work with and the Lazy Question to save your own hours, redirecting the reclaimed time to Great Work.
6. 6Make the redirection a habit, not an event—coach in ten minutes or less, daily and informally, so focus is regained continuously rather than in occasional big pushes.
7. 7Build a fail-safe: when you slip back into taking over or chasing every ping, treat it as a given (everyone stumbles) and return to the filter question on the next trigger instead of abandoning the practice.

Consider the overwhelm circle described in the passages: you're 'pulled in different directions by proliferating priorities, distracted by the relentless ping of email and hustling from meeting to meeting,' and the more you lose focus the more overwhelmed you feel, feeding the loop. The prescribed break is not another productivity hack—'the faster you dig, the faster the world keeps flooding in'—but regaining focus so you and your team 'do the work that has real impact.' Concretely, in your weekly one-to-one, instead of absorbing the problem someone hands you, you ask a focused-and-open question, then 'And what else?' to reveal the real challenge. That keeps you from jumping in and becoming the bottleneck (circle #1), and it directs your energy to the challenge that actually makes a difference. Over ten-minute conversations repeated daily, your team grows autonomy and mastery while you reclaim the time proliferating priorities were stealing. The result the passages promise: you work less hard and have more impact.

• If you have too much work AND people keep needing you, then you've created overdependence—stop taking over and ask a question so they build autonomy.
• If a task has no real purpose or impact, then say no or redirect—doing purposeless work lowers engagement and buries Great Work.
• If you can't name the trigger moment where you default to fixing, then define it (location, time, emotional state, people, or preceding action) before trying to change the behavior.
• If you're tempted to run one more productivity hack, then stop—regain focus instead, because digging faster only lets more work flood in.
• If the conversation can't be coached in ten minutes or less, then it's likely a formal 'It's Coaching Time' event—shrink it to a daily informal act instead.

• Defaulting to advice-giving: you've been 'praised and promoted' for having answers, so you solve the presented problem instead of the real one. Tell: you're talking more than asking.
• Chasing volume over value: you master productivity hacks but stay overwhelmed. Tell: your calendar is full yet the meaningful work never advances.
• Becoming the bottleneck: you help so much that people need you more. Tell: your workload and their dependency both keep rising.
• Treating focus as an occasional event: you do one big priority-clearing then relapse. Tell: overwhelm returns within days because there's no daily habit.
• Quitting after one slip: 'I may as well eat the rest of the cake.' Tell: one missed moment turns into abandoning the practice instead of recovering on the next trigger.

• ▸Active vicious circle: name one—overdependence, overwhelm, or disconnection
• ▸The request/task in front of me: state it in one line
• ▸Impact & meaning check: does this make a real difference? yes/no
• ▸If no—my no or redirect: who owns it instead, or what I decline
• ▸Real challenge (via 'And what else?'): the actual issue under the surface
• ▸Where my energy goes instead: the Great Work this frees me for
• ▸Trigger for next time: when [location/time/emotion/people/preceding action] happens
• ▸Recovery step if I slip: the obvious next action to get back on track

1. 1Diagnose which of the three vicious circles is draining you right now: overdependence (people wait on you), overwhelm (work floods in faster than you clear it), or disconnection (busy work with no meaning). Name the one that fits before changing anything.
2. 2Set the target explicitly as a two-fer: work less hard AND have more impact. If a habit change only reduces your load but weakens results, or only lifts results but adds to your load, it fails the test.
3. 3Shift from giving advice to asking questions — starting by giving 'a little less advice and asking a few more questions.' This is the single behaviour that breaks overdependence by increasing your people's autonomy and mastery.
4. 4Coach in daily 10-minute increments, informally, not as an occasional formal 'It's Coaching Time!' event. Impact accrues through everyday conversations, not scheduled sessions.
5. 5Move conversations from performance to development by adding 'for you' to your questions — e.g. 'What's the real challenge here for you?' This sorts the problem AND builds the person's capability, compounding your impact.
6. 6Raise the TERA Quotient (tribe, expectation, autonomy, rank) in every exchange: ask rather than dictate, let them go first, assume they can find answers. This makes it safer and more useful for both of you.
7. 7Trust that you're being useful even when it feels anxious. Learn to recognize the moment after you ask a question when you feel exposed ('they're going to see right through this') and hold it instead of rescuing with advice.
8. 8Embed the change with real habit mechanics — a specific trigger, a named old behaviour to stop, and the new question to substitute — because insight alone lets the status quo put you back in a headlock.

Goleman's HBR research 'Leadership That Gets Results' names coaching as one of six essential styles with a 'markedly positive' impact on performance, climate and the bottom line — and simultaneously the least-used style. The stated reason: leaders 'don't have the time in this high-pressure economy for the slow and tedious work of teaching people.' The book resolves this apparent contradiction by reframing coaching as the thing that BUYS you time rather than costs it. A manager caught in the overdependence circle finds the more they help, the more their people need help, making the manager a bottleneck. By substituting a question like 'So what's the real challenge here for you?' for a ready answer, the manager stops training reliance and starts building self-sufficiency. The result is the effectiveness outcome: less hard work for the manager, more impact and momentum for the team.

• If a change reduces your workload but weakens your team's results (or vice versa), then reject it — the standard is both work less hard AND more impact.
• If people are excessively reliant on you and you've become the bottleneck, then ask a question instead of jumping in to take over.
• If the conversation is abstract, high-level, full of 'us' and 'we' with no 'me' and 'I', then ground it with 'What's the real challenge here for you?'
• If you feel anxious that questions aren't 'real work,' then trust you're being useful and stay in the question rather than reverting to advice.
• If you're pretty sure you know what someone wants but haven't asked, then ask anyway — assuming the answer breaks the TERA Quotient's autonomy and rank drivers.

• Treating coaching as an occasional formal event; the tell is you scheduling 'It's Coaching Time!' instead of coaching in the flow of a 10-minute conversation.
• Reverting to advice-giving under pressure; the tell is the status quo 'getting you in a headlock' the moment you're back at your desk, doing things exactly as before.
• Coaching only for performance — solving the fire — and never for development; the tell is problems get fixed but no one grows and dependence on you never drops.
• Getting overly theoretical or complex training that never translates to action; the tell is you 'caught up on your email backlog' during the session and changed nothing afterward.
• Delivering coaching that feels like coaching but leaves people worse off; the tell is the BlessingWhite finding — fewer than one in four report significant impact, and 10% report a negative effect ('more confused and less motivated after my session with you').

• ▸Vicious circle I'm in: name overdependence, overwhelm, or disconnection
• ▸Trigger moment: the person/feeling that pulls me into old behaviour
• ▸Old habit to stop: the advice/answer I default to
• ▸New question to substitute: usually a 'What' question ending in 'for you'
• ▸Less-hard test: how this reduces my workload
• ▸More-impact test: how this builds the other person's autonomy or mastery
• ▸TERA move: how I raise tribe, expectation, autonomy or rank here
• ▸10-minute check: how I keep this informal and daily, not a formal event

1. 1Default to a question before advice: when a colleague brings you a problem, ask one of the Seven Essential Questions instead of offering the fix your promotion-trained brain wants to give.
2. 2Ask one question at a time (Masterclass Part 1). Stacking two or three questions muddies the response — pick the single sharpest one and stop.
3. 3Cut the intro and ask the question (Masterclass Part 2). Drop the preamble that softens or leads the question; state the question cleanly and let it land.
4. 4Stick to questions starting with 'What' (Masterclass Part 4). Swap 'why' (which triggers defensiveness) for 'what' to keep the question practical and non-accusatory.
5. 5Get comfortable with silence (Masterclass Part 5). After you ask, stop talking; let the pause do the work rather than rescuing it with more words or your own answer.
6. 6Actually listen to the answer (Masterclass Part 6) and acknowledge it (Masterclass Part 7) before deciding whether another question or a next step is needed.
7. 7Keep each use to a micro-habit under sixty seconds — each of the Seven Questions fits that Double-S (Short & Specific) bill — so you can coach in ten minutes or less inside everyday conversations, not a scheduled 'It's Coaching Time!' event.

Box of Crayons has trained more than ten thousand busy managers in exactly this behaviour change, so treat their own defined trigger as the model: 'When Jenny asks me for feedback on her idea in the team meeting.' That is the specific moment the habit attaches to. Instead of delivering the feedback (the advice reflex that has earned you praise and control for years), you ask one 'What' question and stop. You sit through the slower, less certain pause instead of filling it — the discomfort of feeling like you've 'lost control of the conversation,' which the book reframes as 'empowering.' You listen to Jenny's answer and acknowledge it before doing anything else. The whole exchange takes under a minute, which is why the Seven Questions satisfy the Double-S rule and can be run inside a normal meeting rather than a formal session.

• If your first instinct is to give advice or 'unleash a solution,' then ask a question instead — the reflex to fix is the signal to pause.
• If you're about to ask more than one question, then cut to a single one and ask it.
• If the question starts with 'why,' then rewrite it to start with 'what.'
• If you've just asked and feel the urge to fill the silence, then stay quiet and wait for the answer.
• If you miss the moment or slip back into advice-giving, then treat it as expected (everyone stumbles) and return to the trigger next time rather than abandoning the habit.

• Giving advice because it feels like 'adding value' and keeps you in control — the tell is you leave the conversation feeling certain and useful while the other person did no thinking.
• Stacking questions — asking two or three in a row so the person answers only the easiest — the tell is a scattered or partial response.
• Wrapping the question in a long intro that telegraphs the answer you want — the tell is the person agrees with you instead of thinking.
• Rushing to break the silence after asking — the tell is you answer your own question within a few seconds.
• Making coaching an occasional formal event rather than a daily informal act, or defining the habit too vaguely to trigger — the tell is you 'coach' only in scheduled sessions and the behaviour never sticks.

• ▸Trigger moment: the specific 'When X happens' situation (e.g. 'When Jenny asks for feedback in the meeting')
• ▸Advice reflex to catch: the fix you'd normally blurt out here
• ▸Question chosen: which one of the Seven Essential Questions you'll ask instead
• ▸'What' check: confirm the question starts with 'What,' not 'Why'
• ▸One-question rule: confirm you're asking only this single question
• ▸Silence plan: what you'll do while waiting (stay quiet, count to five)
• ▸Acknowledge step: how you'll signal you heard the answer
• ▸Recovery line: what you do next time if you slip back into advice

1. 1Run the interruption audit: give yourself an hour, half a day, or a day and count how many times you're ready and willing to provide the answer. The benchmark is the doctor's eighteen-second average to interruption — measure yourself against it.
2. 2Name the moment the Advice Monster leaps: the pull toward finding The Answer feels more comfortable than the ambiguity of a question, because your brain prefers clarity and certainty. Notice the physical rush toward advice-giver/expert/fix-it mode.
3. 3Deploy 'And what else?' as your self-management tool. When you're not sure what's going on and need a moment to figure things out, AWE buys you time while keeping you lazy and curious, and it breaks the advice cycle.
4. 4Watch for the disguised-advice trap. Catch yourself asking pseudo-questions like 'Have you thought about X?' — that is advice in a question costume, not curiosity.
5. 5Ask AWE one more time than feels natural. As a rule people ask too few times, not too many; each additional option lowers decision failure. Experiment to find where the well runs dry.
6. 6Acknowledge the answer before moving on — 'Yes, that's good,' 'Nice,' 'Good one' — using call-and-response structure so restraint reads as encouragement, not interrogation.
7. 7Build the restraint into a New Habit Formula: specific trigger, the old advice-giving habit you're stopping, and a sixty-second new behaviour. Practice deeply — small chunks, repetition, and a fist pump when it goes well.

Take the Bob example built through the passages. Trigger: 'When I'm feeling frustrated in my weekly meeting with Bob because he says I haven't really thought about it.' Old habit: 'I ask Bob, Have you thought about X? and hope he gets the suggestion I've disguised as a pseudo-question, all the while thinking bad thoughts about Bob.' That disguised question is the Advice Monster wearing a mask — you've lost restraint without noticing. New behaviour: 'I will ask Bob, So what ideas do you have now?' and then follow with 'And what else?' You stay lazy and curious long enough for Bob to generate options himself. Because adding even one more option cuts decision failure from over 50 percent to about 30 percent, Bob's second and third answers are often the better ones. You acknowledge each — 'Good one' — before asking again, so restraint feels like encouragement.

• If you feel the certainty that you've 'got the answer she needs' before you actually know the issue — that's the Advice Monster; ask 'And what else?' instead.
• If you're about to phrase advice as a question ('Have you thought about X?'), stop — that's disguised advice, so ask a genuinely open question instead.
• If you're unsure whether to ask again, ask one more time — people default to too few rounds, and one more option nearly halves the failure rate.
• If asking makes you feel less in control, let it — that lost control is called empowering; sit with the ambiguity rather than reclaiming it with a solution.
• If there's a genuine place for advice, give it — restraint isn't a vow of silence, it's holding fire long enough for the other person to think first.

• Interrupting inside eighteen seconds. The tell: you're speaking before you actually understand what's going on for the person — the doctor's average, which plenty of managers match.
• Asking AWE in a bored groove. The tell: the words are right but there's no genuine interest or curiosity, and you're not listening to the answers.
• Disguising advice as a question. The tell: you're 'hoping he'll get the suggestion' and thinking bad thoughts when he doesn't.
• Rushing to the next question without acknowledging. The tell: the exchange feels like interrogation, not call-and-response; you skip 'Yes, that's good.'
• Stopping after one round. The tell: you accept the first answer as complete, forgetting that later options are usually the better ones.

• ▸Trigger moment: name the person, setting, and feeling that provokes your urge to advise (e.g. 'frustrated, weekly meeting, Bob').
• ▸Interruption count: tally how many times in your chosen window you were ready to give the answer.
• ▸Old habit to stop: write the exact advice-giving move, including any disguised pseudo-question.
• ▸New sixty-second behaviour: the open question you'll ask instead (must take under a minute).
• ▸AWE round marker: note how many times you asked 'And what else?' before the person ran dry.
• ▸Acknowledgement phrase: your go-to reply to signal you heard them ('Nice,' 'Good one').
• ▸Control check: name the discomfort you felt losing control and confirm you let it stand (empowering).
• ▸Deep-practice note: record when it went well and mark the small win.

1. 1Start with the reason, not the outcome: write a vow connected to serving others (Leo Babauta's frame), not a mental image of success — passages note that imagining the outcome lowers motivation to do the work.
2. 2Anchor a specific trigger using the WHEN THIS HAPPENS format: name the exact moment that fires the new behaviour (e.g., 'After I've asked a question…'), so the habit hangs off an existing event rather than willpower.
3. 3Name the old default you're replacing (the INSTEAD OF): write out the tempting behaviour explicitly, e.g., 'adding another question, and then another,' so you can recognise and interrupt it.
4. 4Shrink the new behaviour to a sixty-second micro-habit: define the smallest complete version — 'Ask just one question. (And then be quiet while I wait for the answer.)' — so it's too small to skip.
5. 5Practise deep and small, not long: repeat the micro-habit many times to interrupt forgetting rather than doing it once for an hour; the passages stress 'practice, practice' and treating the book as something to practise, not read.
6. 6Build a resilience plan for the inevitable miss: decide in advance what you'll do when you slip (check email, add a second question), so a lapse becomes a data point, not a failure.
7. 7Interrupt forgetting deliberately: retrieve the habit in places beyond its origin moment — reflection is a form of practice — to move it from conscious effort toward the 45 percent of behaviour that runs automatically.

Take the one-question-at-a-time habit from the book. The old behaviour is drive-by questioning: after asking one question you pile on another, then another, because they're all good questions and you're curious — and the other person is left dazed, feeling interrogated. To convert this into a durable habit, you set the trigger: 'After I've asked a question.' You name the INSTEAD OF: adding another question. You define the micro-habit: 'Ask just one question, then be quiet and wait for the answer' — a behaviour that takes seconds. You repeat this across every coaching exchange rather than trying to overhaul all your conversations at once, and you deepen it by watching the short reinforcement videos so insight turns into action. Over repetitions the pause after a single question stops feeling like effort and starts running on its own.

• If you catch yourself imagining how great success will feel, then stop and rewrite your reason as a vow to serve a specific person — imagined outcomes sap the drive to do the work.
• If a habit depends on remembering to do it, then it lacks a trigger — attach it to an existing moment using WHEN THIS HAPPENS.
• If the new behaviour takes longer than about a minute, then shrink it until it does; a sixty-second micro-habit gets repeated, a big one gets abandoned.
• If you slip on the habit, then run your pre-written resilience plan instead of restarting motivation from scratch — a lapse is expected, not terminal.
• If you've only practised the habit once, then treat it as unlearned; repetition that interrupts forgetting is what installs it, so build in reflection and retrieval.

• Relying on the twenty-one-day myth — the tell: you assume the habit is 'done' after three weeks and stop practising, so it decays because someone just made that number up.
• Skipping the reason and vaulting to willpower — the tell: your intentions are good but you keep finding the shiraz in your hand, because there's no vow anchoring the change.
• Defining a trigger too vaguely ('coach more') — the tell: you can't say the exact moment it fires, so the behaviour never launches.
• Making the new habit too big — the tell: you plan to overhaul whole conversations and do nothing, instead of a one-minute micro-habit you can repeat immediately.
• Having no plan for the slip — the tell: the first miss becomes 'I've failed at this' and you quit, rather than logging it and continuing.

• ▸Reason / Vow: whom does this serve, and why bother? (connect to a person, not a mental picture of success)
• ▸Old behaviour (INSTEAD OF): the tempting default you keep slipping into
• ▸Trigger (WHEN THIS HAPPENS): the exact existing moment that fires the new habit
• ▸Micro-habit (I WILL): the smallest complete version, doable in sixty seconds
• ▸Repetition plan: where and how often you'll retrieve it to interrupt forgetting
• ▸Resilience plan: what you'll do the moment you slip, decided in advance
• ▸Reinforcement: the reflection or review you'll use to turn insight into action

1. 1Ask one question, then stop talking. Use the habit trigger: 'After I've asked a question, instead of adding another, I will ask just one question and be quiet while I wait for the answer.'
2. 2Cut the intro. Delete the rambling, meandering preamble — the 'preliminary flim-flam' — and get to the question inside seconds, Bond-movie style, not Scheherazade style.
3. 3Start each question with 'What' rather than 'Why.' 'What' keeps the question about the challenge and the person's own read on it; 'Why' tends to put people on the defensive.
4. 4Tolerate silence after asking. The conversation will feel slower and you'll feel less certain you're being useful — sit in that discomfort instead of filling it with another question or your own answer.
5. 5Actually listen to the answer rather than mentally loading your next question or your advice. You've spent years being praised for 'adding value' by talking; suppress the fix-it reflex.
6. 6Acknowledge the answer you get so the person feels heard, then decide whether to go deeper with another single question.
7. 7Close by interrupting forgetting: ask 'What was most useful for you?' to frame the exchange as useful and retrieve the key insight.

You open a one-on-one and feel the Small Talk Tango eating your fifteen minutes — you've burned eight on the weather in Canada. Instead of stacking questions ('drive-by questioning' that feels like an interrogation), you cut the intro and ask one Kickstart Question: 'What's on your mind?' Then you go quiet. The passage explains why this works: whatever the person is holding in mind is using energy and unconsciously narrowing what they can notice and choose — like suddenly seeing red Mazdas everywhere once you're thinking of buying one. The single question acts as a pressure-release valve, making the unformed challenge explicit. You listen to the full answer, acknowledge it, and only then ask one more. At the end you ask 'What was most useful for you?' — which assumes the conversation was useful and interrupts the immediate slide toward 'I've never heard that before.'

• If you notice a second question forming, then hold it — ask one and wait for the answer before deciding whether it's still relevant.
• If you're about to open with a preamble, then cut it and lead with the question itself.
• If you're drafting a question starting with 'Why,' then rephrase it to start with 'What.'
• If silence stretches and you feel the urge to rescue it, then stay quiet — that discomfort is the sound of empowering, i.e. you've handed over control on purpose.
• If a conversation is ending, then ask 'What was most useful for you?' to retrieve and embed the one big insight rather than letting it be forgotten.

• Drive-by questioning: firing multiple questions left and right so there's no time to answer any — the tell is the other person looking dazed and the exchange feeling like an interrogation, not support.
• Rambling intros: a slow, meandering wind-up before the actual question — the tell is you're several sentences in and haven't asked anything yet.
• Filling silence: jumping in with another question or your own answer because the pause feels slow and you're unsure you're useful — the tell is your voice arriving before theirs.
• Reverting to advice: the fix-it habit reasserts itself and you tell instead of ask, because telling has been praised and keeps you in control — the tell is you feel certain and 'in charge' again.
• Not listening: you hear the answer only as a runway for your next question — the tell is you can't recall what they actually said, only what you planned to say.

• ▸The one question (starts with 'What'): write the single question you'll actually ask
• ▸Intro to cut: name the preamble you're tempted to give — then delete it
• ▸Silence plan: how many seconds you'll wait before speaking again (commit to staying quiet)
• ▸'Why' → 'What' rewrite: any 'Why' question reworded to open with 'What'
• ▸Listening cue: a reminder to note their actual words, not your next question
• ▸Acknowledgement line: how you'll signal you heard the answer
• ▸Closing retrieval question: 'What was most useful for you?' (or your chosen variant)
• ▸Habit trigger: 'After I ask a question, instead of adding another, I will ask one and wait.'

1. 1Open with a general inquiry, not a confirmatory one. Ask 'How can I help?' or 'What's the real challenge here for you?' rather than 'I understand you're having a problem with X?'—general openings pull longer, more specific accounts and home in on the real problem.
2. 2Ask one question at a time. After you ask, stop. Don't stack a second or third question; drive-by questioning turns a supportive conversation into an interrogation and buries the real challenge.
3. 3Actually listen to the answer instead of loading the next question. Notice when the riot of internal distraction (planning your next move, wrapping up fast) pulls you off what they're actually saying.
4. 4Treat the first problem presented as the symptomatic or default one. The Focus and Foundation Questions exist 'to get to the heart of the challenge'—assume the opening statement is the surface, not the center.
5. 5Run the 3P model to locate the heart of the difficulty. Ask whether the challenge is really about a Project (the content), a Person (your role in a strained relationship), or a Pattern (a way of working they want to change).
6. 6Start at the Project because it's the most familiar, then test whether the conversation would benefit from moving to the Person or Pattern level.
7. 7Decide, when appropriate, whether to shift from coaching for performance (fixing the specific fire) to coaching for development (the person managing the fire)—the rarer, more powerful conversation that calls them forward to learn, improve and grow.

Box of Crayons' researcher Lindsay found a study contrasting two ways doctors open with patients. Some used a general inquiry—'How can I help?'—while others opened with confirmatory questions like 'I understand you're having some sinus problems today?' With the general inquiries, patients gave longer explanations and mentioned more discrete, specific symptoms, so they were more likely to be homing in on the real problem. The confirmatory opening pre-diagnosed and narrowed the conversation onto the presented symptom before the real issue surfaced. As an added bonus, doctors who asked the general questions received higher patient evaluation scores. The lesson transfers directly: a general opening earns you both more accurate focus on the actual challenge and more respect.

• If you're tempted to confirm the presented problem ('So it's about the deadline?'), then swap it for a general opening and let them define the real challenge instead.
• If the conversation stays on the Project (the content/situation), then test whether a Person or Pattern is the actual heart of the difficulty before solving.
• If you're talking about a person, then remember you're really talking about a relationship and your role in it—focus there, not on fixing them.
• If the aim is only to get something sorted out, that's coaching for performance; if you can call them forward to learn and grow, shift to coaching for development.
• If you've just asked a good question, then ask only that one and stay quiet—don't add another.

• Confirmatory openings: naming the presumed problem up front. The tell—short answers, fewer symptoms surfaced, the conversation locked onto the first thing mentioned.
• Default diagnosis: solving the first, symptomatic problem. The tell—you're already prescribing before they've finished describing.
• Drive-by questioning: firing multiple questions so nothing gets answered. The tell—the other person looks dazed, as in white-knuckled Parisian-roundabout panic.
• Fake listening while distracted: bobblehead nodding and grunts of encouragement while your head plans the next question or a fast exit. The tell—you can't recall the specifics of what they just said.
• Camping on the Project only: staying with the easy, familiar content. The tell—the conversation feels technical and never touches the person or the recurring pattern.

• ▸General opening used: write the broad question you'll ask instead of a confirmatory one.
• ▸First/presented problem: note the surface problem exactly as they stated it.
• ▸Project: what's the content/situation being worked on?
• ▸Person: what's your role in the relationship that's currently less than ideal?
• ▸Pattern: what recurring way of working do they want to change?
• ▸Heart of the difficulty: which P actually holds the real challenge?
• ▸Performance or development: are we fixing the fire or growing the person managing it?
• ▸One question to ask next: a single question—then stop and wait for the answer.