Back to Blog
September 27, 2026 · 9 min read

Questions in the Field

product-managementleadershipcommunicationdiscoveryworkflow

Part 2 of 3: What to Ask, When, and Why It Works

Part 1 of this series covered the foundation: the failure modes, the mindset shift, and what makes a question structurally sound. This post is where it gets applied.

As a product director, you are asking questions in four distinct contexts that each have their own dynamics, stakes, and common pitfalls. Customer discovery. Stakeholder conversations. Strategy and planning sessions. And 1:1s with your team. Each one needs a slightly different approach and each one is a place where better questions produce better outcomes.

In Customer Discovery: Stop Asking About the Future

Discovery is the context most product people think about when they think about asking questions, and it is also the context where the most-repeated advice ("ask open-ended questions") is least sufficient.

The most important rule for discovery: ask about the past, not the future.

"Would you use a feature that did X?" is a question about the future. People are optimistic and helpful in conversation. They will say yes to almost anything that sounds useful. The answer tells you nothing.

"Tell me about the last time you had to deal with X. What did you do?" is a question about the past. It gets you an actual behavior, an actual workaround, an actual pain point. The answer tells you a lot.

The questions I return to most often in discovery:

For understanding the problem:

  • "Walk me through the last time this came up. What were you doing, and what happened?"
  • "What did you do about it? How well did that work?"
  • "How often does this happen? Is it getting better or worse?"

For understanding context and stakes:

  • "Who else is involved when this happens?"
  • "What is the impact (to you, your colleagues, your customers) when it goes wrong?"
  • "If this problem disappeared tomorrow, what would be different about your day?"

That last one is worth dwelling on. "What would be different about your day?" is a question about impact, not features. It grounds you in the real-world consequence rather than the solution space. It reveals the size of the problem you are solving.

For testing your assumptions:

  • "I have heard from others that [X is true]. Does that match your experience?"
  • "Some people we talk to care a lot about [Y]. Is that relevant for you?"
  • "What are we missing? What have I not asked about that matters here?"

That last question, "what have I not asked about that matters", is one I recommend ending each discovery call with. It surfaces things I did not know to ask. Sometimes it produces the most valuable moment in the entire conversation.

In Stakeholder Conversations: Ask What They Need, Not What They Think

Stakeholder conversations are where questions get political. You are talking to people with opinions, competing priorities, and varying levels of trust in you and your team. Asking the wrong question can create conflict.

The first rule: separate what they need from what they think.

Stakeholders often express needs as opinions. "We should launch by Q3" is an opinion. The underlying need might be "we need something to show at the customer conference in October" or "the sales team is losing deals without this capability." The opinion is debatable. The need is workable.

The question that separates them: "Help me understand the reasoning behind that. What is driving the Q3 requirement?"

This question does two things at once. It signals that you are taking the input seriously and opens the door to the underlying need. It does this without sounding like you are pushing back on the deadline.

Other stakeholder questions I have found useful:

For understanding true priorities:

  • "If we could only do one of these things in the next quarter, which would you choose and why?"
  • "What is the consequence if this slips by a month? Two months? What is the threshold where it becomes a bigger problem?"

For surfacing unstated concerns:

  • "What about this direction have we not talked about that makes you nervous?"
  • "What would make you feel confident that this is going in the right direction?"

For alignment after disagreement:

  • "What would you need to see to feel good about moving forward with this approach?"
  • "What is the smallest thing we could do to mitigate the risks you have raised?"

That last question is particularly useful when you are in a disagreement about scope. Rather than arguing about whether to do something, you are asking what the minimum viable output of doing something looks like. It can uncover a path that was not visible.

In Strategy Sessions: Ask What Would Have to Be True

Strategy sessions are where product leaders ask the least useful questions, in my experience. The conversation quickly drifts toward debate with people arguing for their preferred options rather than exploration.

The question pattern that moves from debate back to exploration is this: "What would have to be true for this to be the right answer?"

This is a question borrowed from consulting, and it is worth understanding why it works. When you ask people to defend a position, you get argumentation; they look for evidence that supports the position. When you ask people what would have to be true for the position to be correct, you get the underlying assumptions. These assumptions are the things the argument depends on. And then you can ask which of those assumptions you actually believe.

Applied examples:

  • "We are considering building [X]. What would have to be true about the market for this to be a good bet in the next 18 months?"
  • "If [competitor] is doing [Y], what does that tell us about what they believe? And do we believe the same thing?"
  • "We keep saying [Z is a priority]. What would have to be true for it to be worth de-prioritizing something else to get to it this quarter?"

Other questions for strategy conversations:

For broadening the solution space:

  • "Are we solving the right problem, or are we focused on solving the symptom?"
  • "If we had zero capacity to build and the only option was a change to process or policy, how would we solve this?"

For surfacing assumptions:

  • "What are we assuming about the customer that is not validated?"
  • "What would someone who disagrees with this direction say? Are they wrong?"

In 1:1s: Ask About the Work, Not Just the Status

Most 1:1s are status updates dressed up as conversations. The manager asks how things are going. The direct report gives a summary. Nobody says anything they have not already said in a standup or a Slack message. The 1:1 ends and nothing is different.

The questions are the problem, not the format.

Status questions produce status updates. Questions about the experience of the work produce honest conversations about what is happening.

Questions that go beyond status:

  • "What part of the work right now feels most unclear or frustrating?"
  • "Is there anything you are waiting on from me or from someone else that is slowing you down?"
  • "What is one thing that went well this week that did not get enough credit?"
  • "If you had more time or more support, where would you put it?"

Questions for understanding what people care about:

  • "What kind of work gives you energy right now? What drains it?"
  • "Where do you want to be growing? What does that look like for you?"
  • "What is the thing you are working on that you are most proud of?"

Questions for the relationship itself:

  • "Is there anything I could be doing differently that would make your work easier?"
  • "What is one thing I have done recently that helped you, and one thing that did not?"

That last one requires a relationship that can handle honesty, but if you can build it, it is the most insightful question you can ask a direct report. It treats the relationship as a work-in-progress rather than a fixed dynamic.

One pattern I have learned: ask the question and then be quiet. The instinct in 1:1s is to fill silence, especially uncomfortable silence. Do not fill the silence. The best answers often come after a pause. Jump in too quickly and you lose the thing they were about to say.

The Question You Should Ask More Often Than You Do

I will close with a question that works in almost every context: "What am I missing?"

Do not ask "do you have anything to add". That is a closed-ended invitation to say nothing. Do not ask "any questions?" either; that puts the burden on them. "What am I missing?" is direct, open-ended, and signals genuine curiosity about your own blind spots. It tells the other person that you know your view is incomplete and you would like their help completing it.

In customer conversations, it surfaces information you did not know to ask about. In stakeholder meetings, it uncovers concerns that were not going to get raised otherwise. In strategy sessions, it invites the contrarian perspective that polite rooms often suppress. In 1:1s, it opens the door to things your direct report wanted to say but was not sure you wanted to hear.

It is a small habit with huge impact. Use it more.

The Full Series