Why Should Leaders Ask Questions Instead of Giving Advice?

By Bobby McGraw, Founder of The Becoming Co.

Somebody comes to you with a problem. Before they've even finished explaining it, you already have the answer ready.

I get it. It feels helpful. It feels fast. It feels like leadership.

Here's the direct answer, before we go any further: leaders should ask more questions and give fewer answers, because questions force the other person to do their own thinking, and thinking is what actually builds a leader. Handing someone the answer solves today's problem. It doesn't build the person who has to solve tomorrow's.

That's the whole idea of this article. Growth doesn't usually happen because of the advice we give. It happens because of the questions we ask. Once you see that difference, you can't unsee it in almost every conversation you have with the people you're trying to develop.

The Problem With Always Having the Answer Ready

Here's the tension. Most of us got into leadership, coaching, or ministry because we care about people and we're good at solving things. Somebody's stuck, we see the fix, and it feels almost rude not to say it out loud.

I've done this for years. For a long time I thought my job, when somebody brought me a problem, was to have the answer ready. Fix it fast, hand it over, move on to the next thing. It felt efficient. It felt like I was being useful.

I remember a conversation years ago with someone on my team who came to me stuck on a decision. I had an answer in about four seconds. I gave it. He nodded, thanked me, and then did something completely different two weeks later, because my answer never actually became his conviction. It was borrowed, not built, and borrowed conclusions don't survive contact with a hard day.

The people I've actually watched grow the most weren't the ones I gave the best advice to. They were the ones I asked the best questions of. The ones I kept fixing things for kept coming back with a version of the same problem, just wearing a different shirt.

If we're not careful, we turn ourselves into the answer for everybody around us. And when you're the answer, you become the bottleneck. Nobody grows past the person they keep depending on.

What the Research Says About Questions Versus Answers

This isn't just a feeling. There's real research behind why questions build people and quick answers don't.

Start with memory. Psychologists Norman Slamecka and Peter Graf identified something called the generation effect back in 1978: people remember information far better when they generate it themselves instead of simply being told it. A later meta-analysis of 86 separate studies confirmed the effect holds up consistently, at close to half a standard deviation better recall for self-generated answers over ones just handed over. Translate that into a leadership conversation: the insight someone reaches on their own tends to stick. The insight you hand them tends to leak out by Thursday.

There's also a well documented instinct working against us here. A 2019 study on doctor-patient conversations found that physicians interrupt their patients with advice an average of eleven seconds into the conversation. Eleven seconds. That's not a doctor problem. That's a human problem. We're wired to jump to the fix before we've actually understood the question.

Coaching research backs up what happens when leaders resist that instinct. An interdisciplinary research project called QueSCo, which studies real recorded coaching conversations, has found that contemporary coaching approaches lean on asking questions rather than giving direction, specifically because questioning is what produces a client's change and development. It isn't a soft technique. It's the mechanism.

And this compounds at scale. Gallup's research on the American workplace has found that managers account for at least seventy percent of the variance in how engaged their teams are. Not compensation. Not company perks. Not the mission statement on the wall. The person leading the daily conversations. If that person's daily habit is answering instead of asking, that habit is doing a lot more shaping than any training program ever will.

The Reframe: Advice Gives a Conclusion, a Question Builds a Muscle

Here's the shift I keep coming back to. Advice gives someone a conclusion. A question gives someone a muscle.

A conclusion works exactly once, for exactly this problem. A muscle works every time a similar problem shows up again, whether or not you're in the room.

Think of it in withdrawal and deposit terms. Every time I answer instead of ask, I'm making a small, well-intentioned withdrawal from somebody's growth account. Every time I ask instead of answer, I'm making a deposit. Most days, nobody notices the difference. But run that pattern for a year of conversations, and it's the difference between a team that can only move when you're in the room and a team that keeps moving when you're not.

The Five Questions I Use Instead of Giving Answers

So here's what actually changed for me. I stopped trying to be the smartest person in the conversation and started trying to be the most curious one.

In practice, that means five questions. I didn't invent these because they sounded clever. I use them constantly, in real conversations, because they consistently do the same job: they create clarity, they create ownership, and they hand the thinking back to the person who actually has to live with it.

What are you trying to accomplish? What are you doing to get there? How's it going? Who are you becoming in the process? What is most important right now?

Notice what these questions don't do. They don't solve the problem for anybody. They don't require me to have the right answer, which honestly takes some pressure off. What they do is slow the conversation down just long enough for the other person to hear their own thinking out loud, sometimes for the first time.

I've watched this happen in real time. Someone will start answering "what are you trying to accomplish," stop halfway through, and say something like, "wait, actually, I don't think that's really what I want." That moment doesn't happen when you hand someone an answer. It only happens when you ask a question and then actually wait.

How to Start Asking Better Questions This Week

If you're ready to try this, here's how to actually start.

Pick one recurring conversation. A weekly one on one, a regular check in, a conversation you know is coming. Don't try to overhaul every interaction at once. One conversation is enough to build the habit.

Ask before you offer. Before you give any input, ask one of the five questions. Literally say the words out loud: "what are you trying to accomplish here?" It interrupts the reflex long enough for something different to happen.

Let the pause be uncomfortable. Silence after a real question feels longer than it is. Count to five in your head before you say anything else. Most people will fill that silence with their own thinking if you let them.

Write the five questions somewhere you'll actually see them. A sticky note on your monitor, a card in your notebook, a note on your phone. You will forget in the moment. Everybody does at first.

Notice when you're about to rescue someone. That tightening feeling, the urge to jump in and fix it, is the exact signal to ask instead of answer. Treat the discomfort as the cue, not the problem.

Debrief the habit, not just the outcome. At the end of the week, ask yourself which conversations you defaulted to answering in. You're not looking for perfection. You're looking for the pattern.

Give yourself permission to still answer sometimes. Real emergencies, real expertise gaps, and real deadlines still call for a direct answer. This isn't about never answering again. It's about making questions your default and advice your exception.

The Actual Job

So the next time somebody comes to you with a problem, and you already have the answer sitting right there on your tongue, try something different.

Ask instead.

What are you trying to accomplish? What are you doing to get there? How's it going? Who are you becoming in the process? What is most important right now?

This isn't about becoming less helpful. It's about redefining what help actually means. Help isn't always the fastest fix. Sometimes help is refusing to be the answer so somebody else gets the chance to become one.

You might not solve their problem today. But you might help them grow more than you ever could with an answer. And that was the actual job all along.