Asking Good Questions

Listening as a Skill showed that most of what a manager needs to know is already in the room — someone knows it, but hasn’t said it. Listening lets you catch it when it surfaces. This page is about the tool that makes it surface in the first place: the question.

Questions are the most underrated instrument a manager has. A telling instruction gets you one person’s output. A good question gets you what someone else knows, what they’re worried about, and how they think — three things you cannot get any other way. This page teaches you how to ask so that the answer is worth having: how to open a question instead of closing it, how to push past the first surface reply, and how to keep a question from turning into a trap.

The principle: a question aims at what you don’t already have

When you tell someone something, you transmit what’s in your head. When you ask someone something, you retrieve what’s in theirs — and you rarely know in advance what that is. That is the whole point. A manager who only tells is limited to their own knowledge. A manager who asks well can draw on the knowledge of everyone around them.

So the quality of a question comes down to one test: does it leave room for an answer you didn’t expect? A question that can only be answered the way you already assumed isn’t really retrieving anything — it’s just your own opinion wearing a question mark.

That single test — did I leave room for a surprise? — separates the two kinds of questions we care about most.

Open, closed, and leading

Three shapes. They look similar and do completely different work.

Closed:   "Is the release on track?"            -> yes / no
Open:     "Where does the release stand?"       -> a picture
Leading:  "The release is on track, right?"     -> the answer you asked for

A closed question can be answered in a word — yes, no, a number, a name. It’s useful when you need a specific fact fast: Did the shipment arrive? Is the patient stable? Have you deployed? But used as your main tool, closed questions starve you. “Is the release on track?” invites a “yes” — and a tired, optimistic, or conflict-avoiding person will give you one even when it isn’t.

An open question cannot be answered in a word. It forces the other person to build a picture, and in building it they tell you things you didn’t know to ask about. “Where does the release stand?” makes them walk you through it — and somewhere in that walk is the part that’s actually stuck.

A leading question contains its own answer. “The release is on track, right?” doesn’t ask, it pressures. The person hears what you want to be true and, unless they’re unusually brave, hands it to you. Leading questions feel efficient and are quietly poisonous: they manufacture the agreement you were looking for and teach people that you don’t really want the truth.

The common trap — the confirmation-seeking question

The most common bad question in management isn’t hostile — it’s hopeful. “You’re comfortable with the deadline, yeah?” “That’s basically done, right?” You want a yes, and your phrasing telegraphs it, so you get one. Then you’re blindsided a week later. The fix is mechanical: strip the answer out of the question. Not “That’s done, right?” but “What’s left on that?” The second version can’t be answered with a reassuring nod — it demands the actual state.

Good questions surface what no one said

The reason to prefer open questions isn’t politeness. It’s that the things most likely to hurt you are the things no one has said out loud. A good question is how you go looking for them. Three targets are worth naming.

The real problem, under the stated one. People bring you the symptom, not the cause. “We need another person on the team” is a proposed solution; the real problem might be an unclear priority, a broken handoff, or one task that’s secretly eating half the week. A question aimed under the surface — “What would that extra person spend their time on?” — often reveals that the problem isn’t headcount at all.

The risk no one raised. In most groups, someone senses the thing that’s going to go wrong and stays quiet — because it’s not their area, because the room seems optimistic, because raising it feels like being difficult. A direct open question gives them permission and cover: “What’s the part of this that worries you most?” or “If this fails, where do you think it’ll fail?” You’re not predicting doom; you’re inviting the quiet worrier to speak.

The assumption everyone shared but never checked. The most dangerous belief in any plan is the one so obvious no one said it aloud — the vendor will deliver on time, the customer wants this, the old system can handle the load. Because it was never stated, it was never tested. The question that flushes it out is almost embarrassingly simple: “What are we assuming that we haven’t actually confirmed?”

In practice — the standup that changed course

A team lead runs a routine check-in on a project everyone calls “on track.” Instead of “Any blockers?” (which reliably gets silence), she asks, “If this slips, what’s the most likely reason?” One engineer, who’d said nothing all week, answers: “We’re assuming the client will approve the design by Friday, and they haven’t answered any of our emails.” Nobody had made that a task or a risk. It was the shared, unchecked assumption the whole timeline rested on. One open question surfaced in thirty seconds what a month of status updates had hidden.

The follow-up is where the truth lives

The first answer to any question is almost never the real one. It’s the rehearsed version, the safe version, the top layer. The skill isn’t asking one good question — it’s the willingness to ask a second, gently, into the same spot. Three follow-ups do most of the work:

• “Tell me more about that.” The most powerful four words in the toolkit. It’s not even a question — it’s an invitation to keep going, and it signals that the first answer was welcome, not a verdict. People fill silences and open doors with it.
• “What makes you say that?” This asks for the reasoning behind a claim, not the claim itself. “I think the launch will be fine” is an opinion; “What makes you say that?” reaches for the evidence — and reveals whether there is any. Tone matters enormously here (see the warning below); asked warmly it means help me see what you see, asked sharply it means justify yourself.
• “What would have to be true?” This turns a wish into a plan. Someone says “I think we can finish by Friday.” You ask, “What would have to be true for that to happen?” Now they list the dependencies — and usually discover, out loud, the one that isn’t true yet.

First answer:   "The migration should be fine."
Follow-up:      "What would have to be true for it to be fine?"
Real answer:    "...the backups need to actually restore, and
                 honestly we've never tested that."

Notice the pattern: the surface answer was confidence; the follow-up produced the untested risk. You did not accuse, correct, or contradict. You just asked the person to keep talking into the spot where the truth was hiding.

Questions can be weapons — don’t use them as one

Everything above assumes one thing: that your intent is to understand. The same questions, asked with a different intent, become interrogation — and interrogation shuts people down completely.

There’s a specific kind of bad question every experienced person recognizes: the gotcha. It isn’t asked to learn; it’s asked to expose. “So you didn’t check the logs before deploying?” isn’t a question, it’s an accusation with a raised eyebrow. “Remind me who signed off on this?” isn’t curiosity, it’s a search for someone to blame. People can feel the difference instantly. And the moment they sense a question is a trap, they stop giving you real answers and start giving you defensible ones — hedged, vague, self-protective. You’ve destroyed the very thing questions are for.

The test for yourself is simple: do I already know the answer I want to hear? If yes, you’re probably not asking — you’re prosecuting. Real questions carry genuine uncertainty. If you want to make a point, make the point. Don’t disguise a statement as a question and force the other person to walk into it.

The common trap — the “why did you” question

“Why did you do it that way?” sounds like curiosity but usually lands as an accusation — the person hears you did it wrong. The information you actually want (“what was your reasoning?”) survives better in a phrasing that doesn’t imply fault: “What were you weighing when you chose that?” or “Walk me through the thinking there.” Same information, no defensiveness. When people brace for blame, they stop explaining and start justifying — and you lose the reasoning you were after.

The evidence — safety is the precondition for honest answers

Research into what makes teams effective — Google’s multi-year Project Aristotle study being the best-known example — repeatedly points to psychological safety (a term from researcher Amy Edmondson): the shared belief that you won’t be punished or humiliated for speaking up. The relevance here is direct. Your questions only get honest answers in a climate where honesty is safe. A single gotcha question, asked in front of others, can quietly teach a whole team to stop volunteering the truth. The tool and the climate are the same instrument.

Asking beats telling when you want people to think

There’s a final reason to prefer questions, and it’s about growth, not information. When you tell someone the answer, you solve today’s problem and leave them exactly as dependent as they were. When you ask a question that helps them find the answer, you solve today’s problem and they get slightly better at solving the next one alone.

A manager whose team constantly comes for answers has trained them to. Try, instead, answering a question with a question: “What do you think we should do?” — “What options have you considered?” — “What’s your gut telling you, and what’s making you hesitate?” At first this is slower and mildly uncomfortable for both of you. Over months it compounds: the questions people used to bring you, they now answer themselves, because you spent months handing the thinking back to them instead of doing it for them.

This is the same move as delegation (which we’ll return to in the parts on developing people), just at conversation scale. Every time you resist the urge to supply the answer and ask a question instead, you’re delegating the thinking — the highest-leverage thing you can hand over.

How it connects

Questions and listening are the same skill from two ends: a good question opens the door, real listening walks through it — asking well and then interrupting or judging the answer wastes the whole move. Keep your questions honest by leading with the point when it’s your turn to speak, so you’re not smuggling statements in as questions. And the safety that lets people answer honestly is something you build over time, which is why we over-communicate and tailor the message rather than trusting a single anxious exchange to carry the truth.

Try this

This week, in one meeting or one-on-one where you’d normally ask “Any problems?” or “Is this on track?”, ask instead: “If this goes wrong, where’s it most likely to go wrong?” Then, whatever answer you get, follow up once with “Tell me more about that” — and say nothing else until they do. Notice how much more you learn from the follow-up than from the first reply. Separately, catch yourself once this week about to tell someone an answer they could reach themselves, and ask “What do you think we should do?” instead.

Reflect

1. Think of a recent meeting. Were your questions mostly open, closed, or quietly leading — and what did the shape of them get you?
2. When was the last time an answer genuinely surprised you? If it’s been a while, are your questions leaving room for surprise at all?
3. Is there a risk or assumption on a current project that no one has said out loud? What single open question might surface it?
4. Have you ever asked a “gotcha” question — one where you already knew the answer you wanted? What did it do to the other person’s next few answers?
5. Where are you telling people answers you could be handing back as questions — and what would change if you did?

Show reflections

1. Most people find, honestly, more closed and leading questions than they expected — because those feel efficient. If your questions can be answered with a nod, you’re mostly hearing your own assumptions back. Rewrite one into an open form and notice the difference in what returns.
2. Surprise is the signal that a question actually retrieved something you didn’t have. A long dry spell usually means your questions have narrowed to confirmation-seeking. The fix is to deliberately ask something you truly don’t know the answer to.
3. Almost every project has one — the shared, unchecked assumption the timeline rests on. Good answers name it and name the plain question (“What are we assuming we haven’t confirmed?”) that would drag it into the light before it hurts you.
4. Be honest — everyone has. The point isn’t guilt; it’s noticing the cost: gotcha questions teach people to give defensible answers instead of true ones, and the damage outlasts the moment. The repair is to ask the same thing again later, plainly, with visible good faith.
5. Telling is faster today and expensive over time — it keeps people dependent on you. Strong answers spot a recurring question you keep answering and commit to handing the thinking back once, accepting that it’s slower now to make them capable later.