The Questions Product Managers Should Actually Be Asking

The quality of your product decisions is directly proportional to the quality of your questions.

Not your answers — your questions.

Most product managers are trained to have answers. What should we build? How should we prioritize? When will it ship? The pressure to answer is constant. And the reward for having a confident answer is real — your team trusts you, leadership respects you, stakeholders stop asking.

But confident answers to the wrong questions are worse than no answers at all. They give your team direction — just the wrong direction.

Why Most PMs Ask the Wrong Questions

The default questions are tactical:

• "What should we build next?"
• "How do we improve this metric?"
• "What does the customer want?"
• "How can we ship this faster?"

These aren't bad questions. But they're downstream questions — they assume a strategic context that may not exist.

"What should we build next?" assumes you know what problem you're solving. "How do we improve this metric?" assumes you're measuring the right thing. "What does the customer want?" assumes the customer knows what they need. "How can we ship faster?" assumes you should be shipping at all.

The upstream questions — the ones that challenge assumptions — are where the real leverage is. But most PMs never ask them because the system rewards answering, not questioning.

The Eigenquestion

I use a concept called the Eigenquestion — the one question that, if answered, would change your next decision.

Every team has dozens of open questions. Most are noise. There's usually one that sits underneath all the others. Answer it, and several downstream questions become obvious or irrelevant.

• List every open question. Get them all out.
• Sort by dependency. Which ones depend on other questions? Which one, answered, unlocks or eliminates the most?
• That's your Eigenquestion. Answer it first. Everything else follows.

Five Questions Every PM Should Ask

• "What would make us stop building this?" If you can't answer, you don't have survival metrics. You're building with no exit criteria.
• "Who specifically is this for, and who is it not for?" "Product managers" isn't specific enough. "Mid-market VPs managing their first team of 5-10 PMs" is. The more specific, the better your decisions.
• "What's the cost of getting this wrong?" If the cost is low and reversible, decide fast and learn. If it's high and irreversible, slow down. Most teams treat every decision the same — over-investing in low-stakes choices and under-investing in high-stakes ones.
• "What would have to be true for this to work?" The most powerful strategy question. It forces you to name assumptions explicitly. Once named, you can test them before committing resources to untested beliefs.
• "What decision does this information change?" Ask before running research or building dashboards. If the information won't change a decision, you don't need it.

The Question Framework

Good questions move from upstream to downstream:

• Level 1: Strategy. "Should we be doing this at all?" "Does this fit our strategy?" — Ask before committing.
• Level 2: Direction. "What approach? What trade-offs? What are we optimizing for?" — Ask after committing but before building.
• Level 3: Execution. "How should we implement this? When should we ship?" — Ask only after Levels 1 and 2 are answered.

Most teams jump to Level 3. They're asking "how should we build this?" before answering "should we build this?" That's Product Algebra — assuming the problem and solution are fixed.

Start Here

In your next meeting, before anyone proposes a solution, ask: "What would have to be true for this to work?"

List the assumptions. Then ask: "Which of these have we actually tested?"

The gap between "assumed" and "tested" is where bad product decisions live. Close it, and you'll make better decisions — not because you have better answers, but because you're asking better questions.

Asking the right questions?

In my Eigen Questions workshop, Product and Engineering teams identify the one strategic question blocking alignment. Using AI-assisted analysis, we cut through competing interpretations and find the question that unlocks your team's next move.

Book a Clarity Call — 30 minutes, no pitch. Just clarity on whether your team is asking the right questions.

Not ready for a call? Subscribe to The Adam Thomas for frameworks and honest takes on product leadership, delivered biweekly.