You Were Hired for Your Answers. Now You're Paid for Your Questions

You Were Hired for Your Answers. Now You're Paid for Your Questions.

You got where you are by being the person with the answer. Through most of a career, that's the whole game: know more, solve faster, be the one who can untangle the problem no one else can. Expertise is the currency, and you earned your standing by having a lot of it. So it's disorienting to reach a level where the very thing that built your reputation quietly becomes the wrong move.

Because at some point the job changes underneath you. The work stops being having the answers and starts being getting them out of other people — and those are nearly opposite skills. The instinct that made you valuable for fifteen years, the reflex to jump in and solve, is now the thing that's holding your team back. Not because it stopped being a strength. Because the situation started rewarding a different one.

Why the answer-reflex backfires at the top

When you're the expert in the room and you supply the answer, several things happen that look fine in the moment and cost you over time.

The most obvious: if you always have the answer, the people around you stop developing their own. Why would they wrestle with a hard problem when they know that if they wait, or bring it to you half-formed, you'll solve it? You become the bottleneck — every real decision routes through you, and the team's capacity is capped at your availability. You were promoted to multiply your impact through others, and the answer-reflex does the opposite: it concentrates the thinking back in you.

There's a subtler cost too. When you answer quickly, you close the question — and often you close it before the room has surfaced what it actually knows. Your answer, delivered with the authority of your position, becomes the answer, and the more junior person who saw the flaw in it, or had the better idea, swallows it. You don't even know what you didn't hear. The fast answer feels efficient, but it's frequently buying speed at the price of the better decision that was one good question away.

The shift no one prepares you for

The move from answer-giver to question-asker is one of the least-taught transitions in leadership, and one of the hardest, because it asks you to withhold the thing you're best at.

That's genuinely uncomfortable. Sitting on an answer you're confident is right, and instead asking a question that lets someone else find their way to it — or to a better one — feels slow, inefficient, even like you're not doing your job. Every instinct you built on the way up says solve it, you know how. Learning to ask "what do you think we should do?" and actually wait, or "what are we missing here?" and tolerate the silence, runs against years of wiring. It feels like restraint because it is. But that restraint is the actual work of the senior role — and the discomfort of it is not a sign you're failing at leadership; it's the sign you're finally doing it.

It helps to understand what the question is for. A good question from a leader isn't a quiz or a Socratic game. It does real work: it develops the person answering it, it surfaces information you didn't have, and it builds ownership — people commit to conclusions they reached themselves far more than to answers handed to them. The answer you give solves one problem once. The question you ask builds a person who can solve a class of problems repeatedly. At scale, that difference is the entire job.

When to still give the answer

None of this means becoming a leader who never weighs in, endlessly bouncing questions back while the team waits for direction. That's its own failure — abdication dressed up as empowerment, and teams find it maddening. The skill isn't replacing answers with questions wholesale. It's developing the judgment to know which mode the moment calls for.

Sometimes the room needs your answer: a genuine emergency, a domain where you truly are the only one who knows, a moment when decisiveness matters more than development. The point isn't to suppress your expertise permanently — it's to stop reaching for it by default. The leader who's grown into the role has both modes available and chooses between them deliberately: answer when the situation needs an answer, ask when it needs to build capability or surface what others see. The trap is only having one setting, and for most people who rose on expertise, that setting is stuck on "answer."

Learning to hold the answer

The practical work is mostly about catching the reflex before it fires. Noticing the urge to jump in, and — often — holding it for a beat to ask first. Tolerating the silence after a question instead of rushing to fill it with your own view, because the silence is usually where the other person is actually thinking. Getting comfortable with a team that solves things slightly differently, and sometimes worse in the short term, because that's how they get better, which is the only thing that eventually frees you.

This is hard to install alone, partly because the reflex is invisible to you — it fires before you notice, and from the inside it just feels like being helpful. You experience yourself as a leader who's good at solving problems, not as one who's quietly preventing his team from learning to. An outside view can often see the pattern clearly: where you reach for the answer, what it costs, and what would open up if you asked instead.

You were hired, once, for what you knew. The role you're in now is paid for something harder and quieter: the questions that make everyone around you think better than they would have on their own. The expertise is still there when you need it. The growth is in learning, more often, not to lead with it.

Adriana Georgescu is an executive coach and ICF Master Certified Coach (MCC), one of fewer than 5% of certified coaches worldwide.