The most common management reflex is also the most limiting: when an employee brings a problem, the manager solves it.

It feels productive. It is, briefly. But it's a trap — and once you're in it, it's hard to escape.

The manager who solves every problem becomes the bottleneck for every solution. The team member who gets solved for at every turn stops developing the muscle to solve for themselves. And the manager who spends all their time solving is, by definition, not managing.

Coaching without solving is the counter-intuitive skill that unlocks team capacity — and it's harder than it sounds. The point is not to withhold help; the point is to choose the kind of help that creates future capability instead of immediate dependency.

The Core Shift: Questions Over Answers

The reframe is simple to state and hard to practice: your job is to develop the person's thinking, not to provide your thinking. Your expertise still matters; you are using it to shape the conversation instead of taking over the work.

Jerry Colonna, who coaches executives and wrote Reboot, describes it as staying in the question rather than jumping to the answer. When someone brings you a problem, the instinct is to engage with the problem. The coaching move is to engage with how they're thinking about the problem.

This sounds abstract. Here are the actual question patterns that make it real:

Diagnostic questions:

  • "What have you tried so far?"
  • "What's the core constraint here — what's stopping you from just doing it?"
  • "What would the ideal outcome look like, specifically?"

Reframing questions:

  • "If you were advising a friend in this situation, what would you tell them?"
  • "What would you do if you couldn't fail? What would you do if you couldn't do this at all?"
  • "What does the person you're most trying to impress here think about this?"

Forward questions:

  • "Given everything we've talked about, what do you feel best about doing?"
  • "What's the one thing you could do this week that would move this furthest?"
  • "What support do you need from me, and what do you just need me to trust you on?"

The Pause Technique

One of the most practical tools: when someone brings you a problem, pause for two seconds before responding.

Not to think of an answer — to resist the pull toward solving. Then instead of answering, try one of these:

  • "What do you think we should do?"
  • "Walk me through how you're thinking about this."
  • "What would you do if I weren't here?"
  • "What information would you need to feel confident about this decision?"

If they give you an answer: "That's interesting. What else?" (Push for depth without inserting yourself.)

If they don't know: "What would help you figure that out?"

The goal is always to leave them moving forward, not to leave them with your answer.

The Real Compounding Effect

The reason coaching without solving compounds so powerfully: each time you help someone work through a problem themselves, they come back slightly more capable of working through the next one.

Over a year, this is the difference between a team that brings you problems and a team that brings you options. Over three years, it's the difference between an organization that needs constant direction and one that runs itself.

Julie Zhuo puts it this way: the manager's job is to make your team increasingly capable of making decisions without you. Every time you solve for someone, you borrow against that future.

The leverage is in the coaching, not the solving. That's the trade worth making.