A director I was coaching last year described her one-on-ones this way: “My team comes in with a problem. I solve it. They leave. Repeat.” She was good at it — fast, accurate, efficient. Her team trusted her judgment and her door was always open. She was, by most measures, a responsive and available manager.

She was also the bottleneck for every decision on her team, working 55-hour weeks while her direct reports weren’t growing. She’d created a team that was excellent at bringing her problems and terrible at solving them independently. And the more she solved, the less capable they became, because every answer she gave was a development opportunity she’d removed.

Her problem isn’t unusual. Most managers default to advice-giving because it’s fast, it feels helpful, and it’s what they were rewarded for as individual contributors. The shift from solving to coaching — from giving answers to asking questions that help someone find their own — is one of the most important leadership transitions a manager can make. And it doesn’t require a coaching certification, a new personality, or an hour-long conversation. It requires five questions.

Why Advice-Giving Fails as a Development Strategy

Advice is the natural response when someone brings you a problem. It’s also, paradoxically, one of the least effective development tools a manager has.

When you give advice, three things happen. First, you’re solving based on your context, not theirs. What worked for you in a similar situation may not work for them because their relationships, constraints, and capabilities are different. Second, you’re removing the cognitive work that produces learning. The person who figures out the answer develops the problem-solving muscle. The person who receives the answer develops the asking-for-answers muscle. Third, you’re creating dependency. Every time you solve a problem for a direct report, you’ve subtly reinforced that the path to a good outcome runs through you.

Research supports this. The 70-20-10 model shows that 70% of development happens through on-the-job experience — but only when the experience includes reflection. A direct report who brings you a problem and gets an answer has had an experience. A direct report who brings you a problem, gets asked the right questions, works through their own thinking, and arrives at a solution — that person has had a developmental experience. The questions are the mechanism that turns work into growth.

None of this means you should never give advice. Sometimes the building is on fire and someone needs a directive, not a coaching conversation. The skill is knowing when the situation requires your answer and when it requires your questions — and most managers dramatically overestimate how often it’s the former.

The Five Questions

These aren’t magic. They’re a structure — a sequence that moves a conversation from surface-level problem presentation to genuine thinking. You don’t need to ask all five every time. But having them in your repertoire changes the default from “here’s what I’d do” to “let’s think through this together.”

1. “What’s the real challenge here for you?”

People rarely lead with the real issue. They lead with the presenting problem — the symptom that’s most visible or most urgent. A direct report says “I’m overwhelmed with the Henderson project” and your instinct is to help with the Henderson project. But the real challenge might be that they don’t know how to push back on scope, or they’re afraid to delegate to someone they don’t trust, or they’ve lost confidence after the last project went sideways. This question moves past the presenting problem to the actual development opportunity. The emphasis on “for you” is deliberate — it asks the person to locate themselves in the challenge rather than describing it abstractly.

2. “What have you already considered?”

This question does two things. It honors the thinking the person has already done (which respects their competence), and it reveals their current frame. You learn what options they’ve seen and — just as importantly — which ones they haven’t. If they’ve already considered three approaches and dismissed them for good reasons, you’re having a different conversation than if they haven’t thought beyond the first reaction. It also prevents you from offering advice they’ve already rejected, which is a fast way to make someone stop bringing you problems.

3. “What would you do if you had to decide right now?”

This is the question that makes most managers uncomfortable, because it shifts the decision back to the person who brought it to you. But that’s exactly the point. People often come to their manager not because they don’t know what to do, but because they want permission, validation, or a safety net. This question reveals whether they’re genuinely stuck or whether they have an instinct they’re not confident enough to act on. If they give you a clear answer, your response can be: “That sounds right to me. Go with it.” You’ve just developed their confidence and their decision-making muscle in 30 seconds.

4. “What are you most worried about?”

This question surfaces the anxiety underneath the decision. Most indecision isn’t about not knowing the right answer — it’s about fear of the consequences of the wrong one. The direct report who can’t decide how to handle a difficult client isn’t confused about the options. They’re afraid of losing the account, disappointing the team, or looking incompetent. Naming the fear explicitly makes it manageable. Once it’s on the table, you can address it directly: “If you have that conversation and the client pushes back, I’ll support you. That’s not a career risk.” That’s not advice — it’s the safety net that lets them take the risk themselves.

5. “What will you do, and by when?”

Every coaching conversation needs to end with a commitment. Not a vague intention — a specific action with a timeline. “I’m going to have the conversation with the client by Thursday” is a commitment. “I’ll think about it” is not. This question serves double duty: it creates accountability (you’re going to follow up on Thursday), and it reinforces that the person owns the outcome. They decided. They committed. Your role was to help them think — not to think for them.

What Changes When You Use This Consistently

The shift doesn’t happen after one conversation. It happens over weeks and months as your team recalibrates what to expect from a one-on-one with you. The first few times you ask instead of tell, some people will be frustrated. They came for a quick answer and got questions. That’s fine. The discomfort is temporary. What develops in its place is a team that thinks before they ask, comes with options instead of just problems, and makes decisions at their level instead of escalating everything to yours.

The practical impact on your workload is significant. The director I mentioned earlier tracked her one-on-ones over a two-month period after adopting this framework. In month one, she still answered about 60% of the questions her team brought her. By month two, it had dropped to about 30%. Her direct reports weren’t bringing fewer problems — they were bringing them pre-thought, often with a recommended approach they just needed her to pressure-test. Her role shifted from decision-maker to decision-enabler, and her weekly hours dropped by about six.

The development impact is even more significant. Her team members started demonstrating the kind of independent judgment and strategic thinking that gets people promoted. Two of them were ready for expanded responsibilities within the year — something she attributed directly to the shift from solving to coaching. She wasn’t just managing anymore. She was developing leaders.

When to Coach and When to Direct

Not every situation calls for coaching. Here’s a practical filter:

Coach when the person has the capability to solve the problem but hasn’t fully thought it through, the stakes allow time for reflection, and the development benefit of working through the problem outweighs the efficiency cost of just giving the answer.

Direct when the situation is urgent and time-sensitive, the person genuinely lacks the knowledge or context to figure it out themselves, or the consequences of a wrong decision are severe and immediate. In these moments, give the answer, explain the reasoning, and use the debrief afterward as the development moment: “Here’s why I made that call. What would you have done, and what can you learn from how this played out?”

The ratio should shift as your direct reports develop. A new team member might need 70% direction and 30% coaching. An experienced leader who reports to you should get 20% direction and 80% coaching. If you’re directing experienced people most of the time, you’re either micromanaging or you haven’t developed them enough to operate independently.

Three Things You Can Do This Week

1. In your next one-on-one, replace your first instinct to advise with one question. Just one. When your direct report brings a problem, ask “What’s the real challenge here for you?” before you say anything else. Notice what happens. You’ll almost certainly learn something you wouldn’t have if you’d jumped to a solution.

2. Ask “What would you do if you had to decide right now?” at least once this week. Pick a moment when someone is clearly looking for your answer. Ask the question and wait. The silence might feel uncomfortable. Let it. The thinking that happens in that silence is development.

3. End one conversation with a specific commitment. Before the person leaves, ask: “What will you do, and by when?” Then follow up. The commitment-and-follow-up cycle is what turns a good conversation into lasting behavior change — for both of you.

The five-question framework is a starting point — a practical tool any leader can use immediately. But the deeper shift from manager to coach involves understanding your own patterns (why you default to advice, where your patience runs thin, what triggers your impulse to take the problem back), and that’s where structured coaching and assessment data come in.

Every coaching engagement at TGC&C helps leaders develop this capability — not just how to coach their teams, but how to recognize and work through the patterns that keep them stuck in the advice-giving role.

Learn about our coaching approach →

Want to explore how coaching could help you develop as a leader who develops others? A discovery call is a good starting point.

Schedule a discovery call →