Train the Coaches, Not the Experts
How do organizations build lasting improvement capability? Not by creating more dependence on a few experts, but by developing coaches who help others think, learn, and solve problems independently.
DEVELOPING PEOPLEPROBLEM SOLVINGLEADERSHIP
Train the Coaches, Not the Experts.
When organizations invest in continuous improvement, one of the first instincts is often to create experts.
People who know the methods.
People who can facilitate workshops.
People who can solve difficult problems.
People others can call when something goes wrong.
There is nothing wrong with expertise.
The problem begins when improvement depends on it.
If every difficult problem requires the same few people, the organization may be creating capability—but concentrating it in the wrong place.
The experts become busier.
Everyone else becomes more dependent.
And eventually, the improvement system starts to revolve around a small group of people who are expected to have the answers.
That may produce results.
But it does not necessarily develop the organization.
A different approach is to develop coaches.
A coach does not need to solve every problem.
A coach needs to help someone else learn how to solve it.
That changes the purpose of development.
Instead of asking:
“How do we create more people who know the answer?”
We begin asking:
“How do we create more people who can help others think?”
That is a very different capability.
A good coach knows when to explain and when to ask.
When to challenge an assumption.
When to send someone back to the genba.
When to insist on facts.
When to slow the process down because the team is jumping too quickly to solutions.
And perhaps most importantly, when not to take over.
This is harder than it sounds.
When we know the answer—or believe we do—the fastest route is often to simply give it.
The problem gets solved.
The meeting ends sooner.
Everyone moves on.
But something important may have been lost.
The problem was solved.
The problem solver was not necessarily developed.
That distinction matters.
Because organizations do not become more capable simply by solving more problems.
They become more capable when more people learn how to recognize, understand, and solve problems themselves.
This is where coaching becomes multiplicative.
An expert can solve many problems.
A coach can help develop many problem solvers.
And those problem solvers can eventually help develop others.
Capability begins to spread.
Not through a central department.
Not through dependence on a few specialists.
But through the daily work of the organization.
This does not mean experts disappear.
Technical depth still matters.
Complex problems sometimes require specialized knowledge.
But expertise should support the system, not become the system.
The long-term goal should not be to make the expert indispensable.
It should be to make the organization increasingly capable without them.
That requires a different measure of success.
Instead of asking how many problems the improvement team solved, we might ask:
How many people can now solve problems they could not solve before?
How many leaders are asking better questions?
How many teams can improve without waiting for someone from Continuous Improvement to arrive?
How much capability is being created in the process of getting results?
Those questions tell us something very different about the health of the organization.
Because improvement should not create dependency.
It should create autonomy.
And perhaps that is one of the most important roles of a coach:
to help people reach the point where they no longer need the coach in the same way.
Experts solve problems.
Coaches develop problem solvers.
If we want improvement to spread, we should not only train more experts.
We should train the coaches who can develop everyone else.