Stop Solving the Wrong Problems: The Art of Asking Better Questions

The Curiosity Gap in Team Sessions

A preschooler asks up to 400 questions a day. The average adult asks about 25. Somewhere along the line, we decided that having the answers was more important than asking the right questions.

If you are a product manager leading a strategy session or a team lead running a retrospective, this drop in curiosity is a massive liability. You aren't in the room to have all the answers. Your job is to uncover the real problem before your team spends three sprints building the wrong solution.

Great facilitation isn't about perfectly timing your agenda. It is about asking the kind of questions that get people to open up and challenge their own assumptions.

Listen to Understand, Not to Respond

When you lead a workshop, it is incredibly easy to spend someone else's talking time planning your next move. You are thinking about the clock, the next agenda item, or how to summarize their point.

This is where we miss the critical details. Active listening means giving the room your full attention without formulating your response in advance. When you ask an open-ended question to your team, put your whiteboard marker down.

The pause not only allows the other person to digest your question, but it also shows you are actually trying to understand them. Let the silence do the heavy lifting.

Customers and stakeholders rarely articulate their core problems clearly. They skip straight to surface-level solutions. If you aren't fully present, you will take their first answer as the final truth.

The "Never-Ending Follow-Up" Technique

Harvard Business School professor Dr. Alison Wood Brooks champions a technique called the "never-ending follow-up." It is exactly what it sounds like: you consistently ask a follow-up question based on their previous response.

Imagine a stakeholder in your alignment session insists on a new reporting dashboard. Instead of debating the technical constraints, lean into the follow-up.

• You: What will you use this dashboard to show?
• Stakeholder: The team's weekly sales metrics.
• You: Who else needs to see that report?
• Stakeholder: My manager and two other sales leads.
• You: What happens if the report isn't ready by Monday?
• Stakeholder: Our weekly sales meeting gets delayed.

Suddenly, you aren't building a dashboard anymore. You are solving a meeting delay problem. The conversation changes direction entirely, saving your engineering team weeks of wasted effort.

Make "I Don't Know" Your Superpower

Asking the right questions often uncovers biases and preconceived assumptions you didn't even know you had. It is easy to unintentionally start solutioning based on what you think users need.

The most powerful moment in a product session is often when the person leading it admits they don't know the answer. When you say "I don't know," you invite the engineers, designers, and marketers in the room to step up and collaborate.

If you want to spend less time worrying about how to structure these conversations and more time actually listening to the answers, metodic.io provides the session blueprints to make it happen. Good structure frees you up to be curious.

In your next session, try asking one more follow-up question than feels natural. You might be surprised by what you uncover.