Part 1 of 2: Why Most Questions Miss, and What to Do Instead
There is a skill that shows up everywhere in product leadership — in customer discovery, in stakeholder alignment, in strategy sessions, in 1:1s with your team — and almost nobody talks about it directly.
It is not storytelling. It is not prioritization frameworks. It is not roadmap communication.
It is asking questions well.
I have sat in hundreds of meetings over my career where the right question, asked at the right moment, changed the direction of a conversation. I have also sat in hundreds where a poorly framed question shut a conversation down, put someone on the defensive, or produced an answer that sounded useful but was not.
The difference between those two outcomes almost always comes down to craft — not intelligence, not seniority, not how well you know the subject matter. Craft.
This two-part series is about that craft.
Why Most Questions Miss
Let me start with the failure modes, because they are more instructive than the best practices.
The leading question. This is the most common mistake among experienced people, which makes it particularly insidious. The leading question contains the answer you are hoping for inside the question itself. "Don't you think users would prefer a simpler workflow?" is not a question — it is an opinion in disguise. The other person now has to either agree with you or argue with you, and they will often choose agreement because that is easier. You have just gotten data that confirms your belief rather than tests it.
The multi-part question. "Can you walk me through how you currently handle this process, what the biggest pain points are, and whether you have tried any solutions before?" Three questions at once. The person will answer one — usually the last one — and you will lose the other two. Or they will give you a compressed answer to all three that does not go deep enough on any of them. Ask one question.
The too-soon question. This happens when you ask before the other person has finished developing their thought. Someone starts to describe a problem and you jump to a clarifying question before they have landed. You have just told them, implicitly, that your curiosity is more important than what they were going to say. Slow down. Let them finish. The sentence they were about to say is usually the most important one.
The answer-seeking question. This is subtler. An answer-seeking question is asked to get a specific data point. An understanding-seeking question is asked to understand how someone thinks. "What feature do you wish this product had?" is answer-seeking. "When was the last time you ran into a problem that this product could not help you with — what were you trying to do?" is understanding-seeking. The first gets you a feature request. The second gets you a problem worth solving.
The One Mindset Shift That Changes Everything
I have noticed a pattern in the people I have watched ask questions well: they are genuinely more interested in being surprised than in being confirmed.
Most of us, if we are honest, approach conversations with a hypothesis. We think we already know what the customer will say, what the executive wants to hear, what the engineer is worried about. And so our questions are structured to confirm that hypothesis quickly so we can move on.
The best questioners flip this. They come in hoping to hear something they did not expect. They treat each conversation as an opportunity to be wrong about something. And because they are genuinely open to being wrong, they ask questions that leave room for unexpected answers rather than funneling toward the expected one.
This sounds simple. It is actually a discipline. It requires setting aside the mental model you walked in with and staying curious past the point where you think you understand.
A practical test: after your next customer conversation, ask yourself — did I hear anything that surprised me? If the answer is consistently no, it is worth asking whether your questions are actually open enough to let surprises in.
The Anatomy of a Good Question
A well-constructed question has three characteristics:
It is specific about the situation, open about the direction. The best questions are specific enough to give the other person something concrete to respond to, but open enough that the answer can go anywhere. "Tell me about your workflow" is too vague — people don't know where to start. "Walk me through the last time you had to handle a medication reconciliation issue — what happened?" is specific and open. It gives them a frame (a specific event) without telling them what you want to know about it.
It asks about behavior, not opinion. Opinion questions get you what people think they do or want. Behavior questions get you what they actually do. "How important is real-time data to you?" gets you an opinion. "When was the last time you needed something faster than you could get it — what were you doing?" gets you a behavior. Behaviors are more honest, more specific, and more useful.
It is short. Long questions are usually a sign that you are not sure what you are asking. The cleaner your question, the clearer your thinking. If your question takes more than two sentences to set up, you are probably embedding too much context or too many assumptions. Strip it down. Ask the essential thing.
The Power of the Follow-Up
Most of the value in a conversation comes not from the opening question but from the follow-up — the question you ask after you have heard the first answer.
The most underused follow-up in the world is: "Say more about that."
It sounds almost too simple to be worth mentioning. But it does something specific: it signals that you heard what they said, you are not ready to move on, and you want them to go deeper. People almost always have more to say. They are waiting for permission to say it. "Say more about that" is that permission.
Other follow-ups worth keeping in your back pocket:
- "What do you mean by [word they used]?" — Most conversations have a critical moment where someone uses a word that both parties think they understand but define differently. Find that word and ask about it.
- "What happened next?" — Useful for getting past the summary version of a story and into the specific detail where the real information lives.
- "What would have made that easier / better / different?" — After someone describes a problem or experience, this question opens up the solution space without you introducing your ideas first.
- "Who else is affected by this?" — Expands the frame. Surfaces stakeholders and use cases you had not considered.
What You are Actually Listening For
Good questions are only half the equation. The other half is knowing what to listen for in the answers.
The most useful signals in any conversation:
Emotion. When someone's voice changes, when they lean forward, when they laugh or sigh or use an unexpected word — that is signal. It tells you where the real weight is. Follow it.
Specificity. Vague answers to concrete questions often mean one of two things: the person does not have strong experience with the topic, or they are being careful. Either way, it is worth noting and sometimes worth probing gently.
What does not get said. The question they redirect away from, the part of the story they summarize rather than detail, the scope they don't mention — sometimes the most informative thing in a conversation is a conspicuous absence.
Internal contradictions. People often hold beliefs that are in tension with each other, and they will express both in the same conversation without noticing. Noticing it and asking about it gently ("Earlier you said X, and now you are describing Y — how do you hold those together?") usually gets you to something real.
The Bottom Line
Asking questions well is not a soft skill or a social nicety. It is a core competency for anyone in a role where other people's knowledge and perspective are the raw material of the work. As a product director, almost everything you do depends on your ability to understand what people actually need, want, fear, and believe — not what they say they need, want, fear, and believe when you ask a leading question.
The good news: this is learnable. It does not require a personality change. It requires practice and a genuine decision to prioritize understanding over confirmation.
Part 2 of this series gets into the specific application — the question patterns that work in discovery calls, stakeholder conversations, strategy sessions, and 1:1s. But they all build on the foundation here: ask one thing at a time, be specific about the situation, stay open about the direction, and follow the signal wherever it goes.
Next: Part 2 — Questions in the Field: What to Ask, When, and Why It Works