Why the skills that get you promoted are often the ones that make leadership hardest.

Article 03 in the Leadership Journey Series

 

Most people who get promoted into leadership believe they were chosen because they were excellent at the work.

They were. What nobody tells them is that the work is no longer their job.

And because they know they are excellent at it, they walk into the new role with a high degree of confidence. That confidence is earned. It is also pointed in completely the wrong direction. They are certain they can deliver. They are about to discover that delivering is no longer what is being asked of them.

That gap between what they are confident about and what the role actually requires is where most first-time leaders get into trouble. Not from lack of effort. Not from lack of capability. From a very understandable, very predictable mismatch between the skills that earned the promotion and the skills the promotion demands.

What the organization expects

When a high performer gets promoted, leadership generally expects one of two things. Either the person will replicate their individual success at a team level, raising everyone around them through example and expertise. Or they will manage the work the way they always have, just with more of it flowing through them.

Neither of those is what leadership actually requires.

Leadership requires you to stop doing the work and start building the people who do it. That sounds simple. It is one of the hardest transitions most professionals ever attempt. Because everything that made you excellent as an individual contributor, technical mastery, deep focus, personal accountability, the ability to execute independently, works against you the moment your job is to develop someone else.

The organization rarely explains this. Most promotions come with a title, a pay increase, and a congratulations. What they do not come with is an honest conversation about the fact that the job description just changed completely.

You are no longer being evaluated on your ability to do the work. You are being evaluated on your ability to build people who can do the work without you. That is a completely different job. And you have probably never been taught any of it.

Most new leaders never have that conversation. So they do what feels natural. They keep doing the work.

What the individual gets wrong

The high performer who gets promoted carries their identity with them. The work was the source of their confidence, their status, and their sense of value. When the job changes and the task is no longer theirs to perform, they lose all three at once.

The instinct is to reach back for the task. Not because they are avoiding leadership. Because the task is where they feel competent. The new role does not feel that way yet. So they fill the gap the way they always have. By doing.

Over time the team learns to wait. Why struggle through a problem when the leader will eventually step in and solve it? The leader learns to carry more than they should. Why wait for someone to figure it out when it is faster to do it yourself? Both patterns feel reasonable in the moment. Together they produce a team that does not develop and a leader who burns out.

That is the carrying trap. And it was entirely predictable from the moment the promotion happened without a clear understanding of what the new role actually required.

The knowledge problem

There is a specific version of this trap that technical leaders fall into more than most.

Knowing how to do something well does not mean you can teach someone else to do it. Subject matter expertise gives you the outcome and the what. It does not automatically give you the how in a form that someone else can follow.

Here is why. The expert has compressed years of trial and error, pattern recognition, and accumulated judgment into something that feels like intuition. When they try to teach it, they skip directly to the conclusion because the intermediate steps are invisible to them. Those steps have been invisible for so long that the expert does not know they exist anymore.

This is sometimes called the curse of knowledge. The more deeply you know something, the harder it becomes to remember what it was like not to know it. The steps that feel obvious to you are not obvious to someone who has not lived them. But you cannot see that gap because you are standing on the other side of it.

Process versus application

Technical expertise can help you build a process. That is a real contribution. A well-designed process captures the what and the sequence. It tells someone what to do and in what order.

But a process does not teach judgment.

It does not teach someone what to do when the situation does not match the process. It does not teach them how to recognize which part of the process applies to the problem in front of them. It does not teach them what to do when step three fails and step four assumes step three succeeded.

That gap between following a process and applying judgment is where most team members live when they are still developing. The expert leader sees the gap and fills it themselves because it is faster and easier than explaining it. Over time the team member never develops the judgment because the leader keeps filling the gap for them.

The process exists. The application never develops. And the leader cannot understand why because the application feels so obvious.

Knowing the work deeply is a necessary but not sufficient condition for teaching it. In many cases, being excellent at the task actively works against developing the people who need to learn it.

The correction instinct

Technical expertise often rewards precision and correctness. There is a right answer. You either know it or you do not. When you are teaching someone and they get it wrong, the instinct is to correct them immediately and show them the right way.

That feels like teaching. It is actually the opposite.

Real development requires allowing someone to work through the problem, make the mistake, and understand why it was a mistake. That process is slow and uncomfortable for someone who can see the right answer from the beginning. The instinct to correct is one of the biggest barriers to developing the judgment a team needs.

Judgment does not develop from being told the answer. It develops from working through the problem long enough to understand why the answer is the answer.

The conversation that almost never happens

The promotion trap has three parts. The organization selects for the wrong criteria. The individual misunderstands what they were selected for. And neither party has the honest conversation that would close the gap.

Most organizations do not have that conversation because they assume competence at one level predicts competence at the next. Most individuals do not have it because they do not know what questions to ask. So the gap stays open, the carrying trap closes around the new leader, and everyone wonders six months later why someone so talented is struggling.

The answer is usually sitting right there in the promotion announcement. We selected this person because they are excellent at doing the work. We just forgot to tell them that doing the work is no longer their job.

The next article in this series begins to address what the new job actually looks like. Specifically, how a leader starts to make their own thinking visible so it can become something they develop in others rather than something they keep doing themselves.

But before we get there, a question worth sitting with.

When you were promoted, did anyone tell you that the job had changed? And if not, how long did it take you to figure it out on your own?

 

About this series

This is the third article in the Leadership Journey series. Article 01 introduced the challenge of transitioning from individual contributor to leader. Article 02 examined the environment that shaped your own development and the honest question of whether you have built anything like it for your team. Article 04 will explore how to begin making your own thinking visible so it becomes something you can develop in others.