Why High Performers Struggle When They Become Managers

For many high-performing professionals, becoming a manager feels like the natural next step in their career. You’ve built a reputation for being reliable, responsible and dedicated. When you’re given a task, you get your head down and get it done. You take your commitments seriously and the idea of letting people down sits heavily with you.

So when the promotion comes, it usually feels like recognition for exactly those qualities. It’s easy to assume the next role will simply involve doing more of the same work, just at a higher level.

What many high performers discover, often quite quickly, is that leadership doesn’t work like that at all.

Up to this point in your career, most promotions have probably followed a fairly natural progression. A junior role becomes a more experienced one. Expertise grows, autonomy increases and the tasks become more complex or more important. But the underlying work is still familiar.

For software engineers and technical specialists, this pattern is particularly consistent. Every step up has rewarded deeper expertise: knowing more, solving harder problems, being the person others come to for answers. Moving into management feels like it should be another step along that same path.

In reality, it’s something quite different.

Instead of being responsible primarily for your own output, you now depend on the work of other people. People who may approach tasks differently from you. People who may not have the same level of commitment or urgency you’ve always held yourself to. People who might solve problems in ways you wouldn’t choose.

For someone used to delivering reliably through their own effort, this can feel deeply uncomfortable.

The responsibility is still yours, but the control over how things unfold suddenly isn’t. If something goes wrong, you’re the one held accountable.

That’s where the self-doubt usually starts.

Sometimes they take work back themselves, telling themselves it’s simply faster if they do it personally. At least then they can be sure it’s done properly.

It’s rarely about ego or mistrust. It usually comes from a strong sense of responsibility. If the team doesn’t deliver, it’s the manager who feels accountable.

The problem is that this approach quickly becomes unsustainable. Trying to control everything is exhausting for the manager and frustrating for the team. Instead of feeling trusted to do their work, people start to feel micromanaged, and the manager ends up overwhelmed by the sheer volume of things they’re trying to stay on top of.

Another pattern appears in how these managers judge their own productivity. If they finish a day full of conversations, meetings and supporting their team, they often feel strangely dissatisfied. Even if those conversations were productive, the absence of tangible output leaves them feeling like they didn’t really achieve anything.

For technical people especially, a day without something concrete to show for it can feel like a day wasted.

Looking back at my own transition into leadership, I recognise many of these patterns.

For most of my career, I’d either built the software myself or managed small enough teams that I could get across the work quickly. I knew the codebase, I knew the history, I knew where the bodies were buried.

And I’ll be honest: I was good. I held high standards and I knew I could deliver to them. It was easier to do things myself than explain them, faster to fix something than wait for someone else to, and simpler to stay close to every little detail than risk something slipping through.

Then I started a new job responsible for a platform I hadn’t built and a team I hadn’t hired. The codebase was ten years old, heavily customised per client, and complex enough that understanding it properly meant knowing its entire history. One class alone was 20,000 lines of code.

Every instinct I had said: get across it. Learn it. Be the expert. Because that’s how high performers operate. You roll up your sleeves, you get into the detail, and whatever goes wrong, you know you can fix it. That ability to step in and save the day is the safety net you’ve always carried with you.

I hated that I couldn’t do that here. I didn’t fully understand what the team were working on. I couldn’t always tell whether something was going to cause a problem until it already had. I wasn’t in control in the way I was used to being, and I had no idea how to feel useful without that.

I had no choice but to trust the people who already knew it.

Gradually something surprising happened. The work didn’t fall apart. In many cases it improved. People took more ownership, brought ideas I wouldn’t have thought of myself, and grew into responsibilities I’d have previously held on to. The less I tried to control, the better things seemed to work.

Leadership became far less exhausting. And for the first time, I actually started to enjoy it.

The biggest shift managers need to make sounds obvious when you say it out loud, but it’s surprisingly easy to miss. 

Earlier promotions in a career often involve building deeper expertise. Becoming a manager, however, requires developing an entirely new set of capabilities. The focus moves away from producing work personally and toward creating the conditions where other people can do their best work.

That means developing skills that may not have been necessary before. Skills like delegating effectively, having difficult conversations, setting direction and building trust within a team.

It also means accepting that people will approach tasks differently from you and that good enough is often exactly what’s needed.

When leaders realise this is a different job altogether, something interesting often happens.

They start stepping back from the detail, sometimes reluctantly at first. As they give their team more space, they begin to see that the people around them are far more capable than they originally believed.

Confidence grows on both sides. The manager becomes more comfortable not knowing every answer, and the team becomes more confident taking ownership of their work. Each time the team handles more responsibility well, it becomes easier for the manager to let go a little further.

Leadership starts to feel calmer. Instead of constantly firefighting or worrying about things slipping through the cracks, the focus shifts toward guiding the direction of the work and supporting the people responsible for delivering it.

For many leaders, this is the moment when the role finally begins to feel manageable. And sometimes even rewarding.

Leadership requires a different approach.

The encouraging part is that the qualities that made you successful in the first place – responsibility, dedication and the desire to do good work – are still incredibly valuable. They simply need to be applied in a different way.

If you’re finding that the approach that’s always worked for you isn’t producing the same results in a leadership role, leadership coaching can help you figure out what’s not working and how to lead more effectively without abandoning everything that made you good at your job.