When Expertise Gets in the Way of Better Coaching

Experience is supposed to make leadership easier.

You recognize patterns faster. You know what tends to work. You can often see the solution before the other person has finished explaining the problem.

That is usually an advantage.

Until the moment calls for coaching.

Then the same expertise that makes you effective can become the thing that gets in the way.

Why experienced leaders solve so quickly

Most leaders have spent years being rewarded for finding answers.

You diagnose problems.

You make decisions.

You give advice.

You keep things moving.

Over time, usefulness can become closely connected to being the person who knows what to do.

Then coaching asks something different of you.

Instead of answering, you ask.

Instead of speeding things up, you leave space.

Instead of solving the problem for someone, you let them think through it themselves.

That shift can feel surprisingly uncomfortable.

The discomfort is not necessarily a sign that coaching is going badly.

Sometimes it is a sign that you are resisting a very well-practiced instinct.

The problem with giving the answer too quickly

There are plenty of situations where someone genuinely needs your expertise.

But there are also moments when giving the answer immediately solves the wrong problem.

You may solve the issue in front of you while removing the other person’s opportunity to develop their own judgment.

That distinction matters.

There is a difference between helping someone fix today’s problem and helping them become better at thinking through tomorrow’s.

Even when your advice is correct, handing it over too quickly can short-circuit that process.

The challenge is not to pretend you do not have expertise.

It is to become more intentional about when you use it.

Are you asking a question, or giving advice?

One of the easiest habits to fall into is disguising advice as a coaching question.

You may hear yourself saying:

“Have you thought about speaking to them directly?”

“What if you moved the deadline?”

“Could you delegate that?”

These are technically questions.

But often, we already know the answer we want.

The question is simply a softer way of steering someone toward our own solution.

A useful test is to ask yourself whether you are genuinely curious about what the other person might say.

If not, it may not really be a coaching question.

Sometimes the question is really just advice with a question mark at the end.

Try one small pause

A useful place to practice this is when someone asks:

“What do you think I should do?”

Most of us move quickly into answer mode.

Instead, try pausing and saying:

“I have some thoughts, but before I share them, what are you thinking?”

That does not mean refusing to give your opinion.

It simply changes the order.

You create space for their thinking before adding yours.

You may discover that they already have a good idea.

You may hear an option you had not considered.

Or you may simply help them become more confident in their own reasoning.

The point is not to withhold expertise.

It is to avoid using it so quickly that no one else gets to think.

Coaching first does not mean coaching always

There is an important limit to all of this.

Not every situation calls for coaching.

Sometimes someone needs your answer.

Sometimes they need a decision.

Sometimes they need clarity rather than another question.

A leader who insists on coaching in every situation can be just as unhelpful as one who always gives instructions.

Good coaching means having another response available to you, not replacing every other form of leadership with questions.

The real skill is judgment.

Do they need to think?

Do they need your experience?

Do they need a decision?

Do they need space?

Or do they simply need you to tell them what happens next?

Coaching is built in ordinary moments

This is also why leadership development can fall short when it is treated mainly as an event.

We send people on courses.

We run workshops.

We teach models and frameworks.

Then we send managers back into work and hope the behavior sticks.

But coaching is a behavior, and behaviors are built through repetition.

The more useful question may not be:

Have our managers learned how to coach?

It may be:

Where are they actually practicing it?

In one-to-ones?

After mistakes?

During career conversations?

When someone disagrees with them?

When they are under pressure?

Those moments tell us far more than whether someone can describe the right coaching technique.

Practice the behavior you want to build

AI can also be useful here, not as a substitute for a difficult conversation, but as a practice space.

Before a conversation, you could use it to rehearse.

Afterward, you could use it to reflect.

Did you give advice too quickly?

Did you interrupt?

Did you become directive under pressure?

Did you fill every silence?

The human still has to do the difficult part.

You still have to walk into the room and have the conversation.

But practice becomes easier to repeat when you have somewhere to experiment, make mistakes, and try again.

One thing to unlearn this week

You do not need to transform your coaching style overnight.

Choose one habit.

Maybe you interrupt.

Maybe you solve too quickly.

Maybe you ask too many questions.

Maybe silence makes you uncomfortable.

Or maybe you keep coaching when what someone really needs from you is clarity.

Notice it in real conversations.

Then experiment with doing something slightly differently.

Because mastery is not simply knowing what good coaching looks like.

It is noticing what happens when your instincts kick in and becoming capable of choosing a different response.

Sometimes the most useful thing you can do with your expertise is share it.

And sometimes the most useful thing you can do is wait.