Why Helpful People Ask Bad Questions

I recently took the Co-Active Fundamentals course. Eight hours on Zoom learning how to be a better coach.

It was a good reminder of something most of us already know and still rarely do.

Someone brings you a problem. You listen just long enough to get the gist, layer on your own experience, and respond with a solution or a pointed question designed to steer them somewhere.

You're being helpful. You're being efficient. You're also, often, being useless.

Not because the advice is bad. Because you skipped the part where you figured out what the other person actually needed. You diagnosed in three seconds and prescribed in five. Great in a board meeting. Terrible in most other conversations.

The Co-Active course did not teach me anything radically new. It just made me notice how often I do this myself.

So here are a few reminders that might hit differently if you're honest about your defaults.

Listen to Learn, Not to Respond

One of the core ideas behind Co-Active is that people are naturally creative, resourceful, and whole. They already have their answers. Your job is not to supply the answer. It is to help them find it.

That is a coaching concept, but it applies everywhere.

The friend venting about their job is not filing a support ticket. The engineer frustrated about a project is not looking for your three-step plan. Your partner telling you about a hard day does not need you to optimize tomorrow by 9 a.m.

Most of the time, people just need to be heard well enough that they can hear themselves think.

Co-Active breaks listening into three levels:

• Level 1: Internal Listening. You're hearing words, but your attention is on yourself. What does this mean for me? What should I say next? Do I agree? This is autopilot. Most conversations live here.

• Level 2: Focused Listening. Your attention is fully on the other person. Their words, their tone, their pauses. You're taking in what they are actually saying without filtering it through your own experience.

• Level 3: Global Listening. You're taking in the full picture. Body language, energy shifts, what they are not saying. The moment they get quieter, rush past something, or cross their arms. You're reading the whole person, not just the words.

Most of us are better at Level 2 than we think. We notice things. We pick up on tone. We remember details.

The gap is what we do next.

The default is to take everything we noticed and use it to relate. Someone tells you about a rough week, and you match it with your own. "Oh man, same thing happened to me when..."

Good intentions. Wrong move.

It shifts the conversation from their thing to your thing.

"What was the worst part?" lands differently than "Yeah, I went through the same thing." One opens a door. The other closes it and opens a different one with your name on it.

Suspend Your Beliefs Before You Respond

This is the step between listening and responding. Most of us skip it.

You've heard someone out. You have a read on the situation. If you're a founder, you probably think you already have the answer. If you're a manager, you've seen this movie before. If you're a parent, you definitely think you know better. You probably do not. But it feels like you do.

The instinct is to move straight to synthesis. Hear the problem, pattern-match against your experience, respond with your take.

That works when someone explicitly asks you to make a call.

It does not work when someone is trying to think out loud and you hand them a conclusion before they finish the thought.

Co-Active asks you to do something harder: suspend your beliefs.

Not abandon them. Just set them aside long enough to stay curious before you layer in your own interpretation.

Why this matters: the moment you start filtering through your own lens, every question becomes a guided tour to your conclusion.

You've seen this in sales calls. But it also happens in 1:1s, "Don't you think the real issue is...?" In friendships, "Have you tried just...?" At the dinner table, "Why don't you just...?"

All of those are opinions dressed up as questions.

A genuinely useful question is one where you do not already know the answer. You're asking because you're curious, and you're willing to let their answer change your mind.

That takes maybe 30 seconds of restraint.

A surprising number of great conversations, whether in a sprint retro or over drinks, happen because someone held their take just long enough to hear something unexpected.

Match the Question to Where They Are

You've listened. You've held your beliefs. Now what?

This is where the question actually matters, and where most advice on "asking better questions" falls short.

The type of question has to match where the other person is.

A great question at the wrong moment just bounces off. It is like offering someone a map when they are drowning.

Co-Active frames this around three things people are usually navigating: fulfillment, balance, and process.

You do not need to remember those terms.

The practical version looks like this:

🧭 The Question Compass

This plays out everywhere:

• A direct report says they're "fine" but clearly is not. They do not need your next clever question. They need you to name what you see: "You don't seem fine. What's going on?"

• A cofounder is stuck on a strategic decision and going in circles. They do not need more data. They need: "What would you do if you had to decide by Friday?"

• A friend says they hate their job but will not do anything about it. They do not need your LinkedIn tips. They need: "What's actually stopping you?"

• Your partner is overwhelmed after a brutal week. They do not need your plan for Saturday. They need: "What would feel good right now?"

Most of the time when your help does not land, the question was not bad.

The diagnosis was.

Respond to the Person, Not the Problem

When someone tells you about something they're dealing with, there are two things you can respond to.

1. The problem is the surface-level thing they said. The delayed launch. The missed hire. The fight with their partner.

2. The person is what is underneath.

A teammate says: "I'm frustrated because the product launch keeps getting delayed."

• Responding to the problem: "Have you tried breaking the milestones into smaller chunks?"

• Responding to the person: "What's the frustrating part for you? Is it the delay itself, or something else?"

The first answer might be useful. But it assumes the issue is the timeline.

Maybe the real issue is ownership. Burnout. A lack of confidence in the direction. You will not find out if you're too busy solving.

Same thing outside work. A friend complains about always being tired. You could suggest a sleep app. Or you could ask, "What's draining you?"

Those are very different conversations.

The instinct to solve feels generous. Sometimes it is.

But the faster you are at solving, the more likely you are to solve the wrong thing confidently.

Your Reminders

1. Listen to learn, not to respond. Use what you hear to ask a question, not to share a parallel story.

2. Suspend before you respond. Am I about to ask a genuine question, or make my point in question form?

3. Diagnose the moment. Options, clarity, heard, or push.

4. Respond to the person, not the problem. Ask about what is underneath before you solve what is on top.

5. Use the 60-second rule. Resist solving for one full minute. It is harder than it sounds.

Final Thought

Most people do not need better answers. They need better questions.

And the best questions usually do not come from being smarter. They come from being curious long enough to understand what is actually needed before you try to help.

If you're curious about Co-Active coaching, check out the Co-Active Training Institute. If you want more stuff like this, subscribe to Work in Progress.