The Answer Is the Bottleneck

I watched a conversation between one of my senior leaders and a leader who reports to him. The other leader had walked in with a problem and a clear expectation: tell me what to do. My senior leader had the answer. He had the experience, and handing it over would have taken thirty seconds. I could see the instinct right there on his face.

Then he stopped himself and asked a question instead. A good one. It sent the other leader deeper into the problem instead of toward a solution someone else had already formed. He walked out with his own thinking more fully developed, not with his boss's answer standing in for it.

Nobody else would have noticed that moment. I did, because I know how hard it is. I still miss it more often than I'd like to admit.

I'm task-oriented by nature. Someone brings me a problem, I see the answer, and everything in me wants to hand it over and move to the next thing on the list. For most of my career that felt like good leadership. It was fast. It was usually right. People left my office with what they came for.

What I didn't see for a long time was what it cost them. Every time I gave someone an answer they could have found on their own, I made them a little more dependent on me and a little less capable without me. That isn't leadership development. That's a bottleneck with a title.

This isn't a policing problem. It shows up in hospitals, in high-pressure sales, in fast-growing companies, anywhere the pressure is constant and results are watched closely. We promote the people who are best at the work, then we keep rewarding them for the thing that got them promoted: solving problems fast. When performance gets prioritized over people, the leader with all the answers looks like the strongest leader in the building. David Finkel put it bluntly in a piece for Inc.: if your team can't function without you in the room, you have a dependency, not a team.

Dr. Bill Dickinson of C3 Leadership makes the same point from the development side. Leaders promoted for individual excellence tend to keep doing exactly what earned them the promotion. They solve problems instead of building problem-solvers, and they give answers instead of asking questions. Gallup's research suggests only about 2 in 10 managers instinctively know how to coach. The encouraging part is that coaching isn't a personality trait. It's a skill, and skills can be learned.

Coaching also isn't soft leadership. Standards stay. Accountability stays. Hard conversations still happen. What changes is the question underneath them. Instead of only asking how do I correct this, a coaching leader also asks how do I develop this person.

So what does that look like day to day? Here's what I practice, and what I still have to remind myself to do.

Start by holding the answer. When someone asks what they should do, don't respond with a solution right away. Ask what options they've already considered. Ask what they'd do if you weren't available. Ask what the next step could be. You aren't dodging the question. You're building the muscle they'll need next time, when you're not in the room.

When you do have ideas, say so, and then wait. There will be moments when you clearly see the path and holding back feels like withholding. One line I lean on: "I have some ideas, but I'd like to hear yours first." It keeps your experience on the table without letting it take over the conversation. More often than you'd expect, they get there on their own.

Listen for the question behind the question. The problem someone brings you is rarely the whole story. It's usually sitting on top of something they haven't fully named yet. Ask one more question than feels comfortable, then let the silence sit longer than your instincts want. In my experience, what matters most tends to show up in the pause after a question, not in the question itself.

Be clear about the outcome and loose about the method. Most of us were promoted because we had a way of doing the work, so when we look for something valuable to give our people, our method is what we reach for. But if someone gets to the result you needed by a different route than you would have taken, let it stand. Correcting a method that produced a good outcome teaches people to wait for you instead of thinking for themselves.

Make it a rhythm, not a moment. Coaching doesn't happen in one conversation. It happens in regular one-on-ones that aren't status updates. I like to close them with two questions: What support do you need from me? What feedback do you have for me? A lot of people have never been asked either one by the person they report to. The answers will tell you more about how you're leading than any report will.

There's one more tool, and it's the one that made the others possible for me: get coached yourself. I didn't learn to hold the answer by reading about it. I learned it sitting across from someone who asked me questions I wasn't asking myself and had no interest in handing me his answers. Being on the receiving end of good coaching showed me how much a well-timed question can do, and how rarely leaders at the top ever get asked one. It's a big part of why I became a Certified Business Coach and why coaching senior leaders is now a core part of my work. If you're wondering whether a thinking partner like that could help you, or the senior leaders around you, become better coaches of your own people, here's how I approach executive coaching.

That brings me back to the conversation with my senior leader. I never coached the person sitting across from him. I didn't have to. What started years earlier with one coach and one leader showed up in a conversation I was only watching. That's what coaching does when it takes hold. It multiplies. Answers solve today's problem. Questions build the people who will solve the next one.

Here's what I'd ask you to try this week: the next time someone brings you a problem you already know how to solve, hold the answer and ask one question first.

What's a question someone asked you that changed how you thought about a problem?

#Leadership #LeadershipDevelopment #ExecutiveCoaching #Coaching #PeopleLeadership

Next
Next

Intent Doesn't Land. Impact Does.