Someone reporting to me was better at this than I was

One of the best people managers I have worked with reported to me.

He was responsible for a team of roughly two hundred people, most of them fresh graduates or professionals with only a few years of experience. Anyone who has managed a group like that will understand the challenge. There is energy and ambition, but also uncertainty. People are learning the work while learning themselves. They need direction, reassurance, correction and room to grow, often at the same time.

He handled that responsibility with an extraordinary degree of grace.

He had a natural ability to put young professionals at ease. People felt heard around him. He could bring calm without lowering standards and create the conditions in which someone still finding their feet could begin to trust their own ability.

I learned a great deal by watching him.

That admission matters. He reported to me, but in this part of management he was better than I was. His position in the organisation did not change that truth, and my position did not make acknowledging it any less necessary.

Authority and competence are different things

An organisation chart is useful. It shows reporting lines, accountability and the formal route through which decisions travel.

But it does not show who is best at every part of the work.

The person with the highest title may carry the broadest accountability. That does not mean they have the strongest judgment in every situation, the deepest technical knowledge or the best instinct for every group of people.

On most capable teams, expertise is scattered. One person understands a client better. Another can see the operational consequence of a decision before anyone else. Someone else can explain a difficult idea with unusual clarity. A colleague closer to the work may recognise friction that remains invisible from a leadership meeting.

The reporting line tells us who is accountable. It does not tell us where competence has been distributed.

Confusing those two maps can make a team smaller than it really is.

Why this can feel uncomfortable

Seniority creates expectations, including expectations we place on ourselves.

After a promotion, it can feel as though we are expected to have the answer. Admitting that someone junior sees something more clearly may feel like surrendering authority. Praising a team member's skill too openly may even trigger the private worry that others will begin comparing it with our own.

I do not think those reactions make someone a bad leader. They make them human. But if we allow the discomfort to govern us, the cost is paid by the whole team.

People soon learn whether their capability will be welcomed or contained. If every good idea has to be translated into the manager's voice before it can be accepted, contribution becomes cautious. If credit always moves upward while correction moves downward, people stop bringing their best thinking.

The leader may remain visibly in control while becoming progressively less informed.

Recognition does not diminish authority

Watching that manager lead his team did not make me feel that I had less to offer. It gave me access to a form of leadership I wanted to understand better.

This is one of the unexpected freedoms of becoming more secure in a role. We no longer need every strength in the room to belong to us.

We can say, plainly, that someone is excellent at something. We can ask how they approach it. We can allow them to shape the method rather than merely execute our instructions. We can give credit without adding a reminder that we remain accountable.

None of this removes the manager's responsibility. Leadership still requires judgment about whom to trust, when to intervene and how the different strengths of the team should come together. Recognising competence is not abdication. It is part of using authority well.

Let the person with the strength influence the work

Recognition becomes meaningful when it changes how work is done.

If someone has a better instinct for developing early-career colleagues, invite them to shape that approach. If another person understands a client more deeply, let that understanding influence the plan. If a team member repeatedly sees a risk or dependency that others miss, make room for that perspective before the decision is fixed.

It can help to ask:

  • Who on this team is strongest at this particular problem?
  • What can they see that my role may be keeping me from seeing?
  • Am I asking for their judgment, or only asking them to carry out mine?
  • Will the credit for the result remain attached to the person who contributed it?

The answers reveal whether we are using the team's capability or merely supervising it.

A team should be allowed to exceed its leader

There is something deeply encouraging about discovering that a person reporting to you can do part of the work better than you can.

It means the team contains more ability than any one individual. It means leadership does not have to be a performance in which the manager proves, repeatedly, that the hierarchy was correct. It can become the quieter work of recognising strength, placing trust and helping excellence travel further.

I would still doff my hat to that manager as one of the best people leaders I have encountered. Saying so does not reduce what I brought to the relationship. It honours what he brought to it and what I was fortunate enough to learn.

The org chart describes positional authority. It does not distribute competence.

Good managers know the difference, and their teams become stronger because they do.