Stop Promoting Your Best Technician Into Management

The best engineer on your team just got promoted to Engineering Manager.

Congratulations.

You've now taken your best engineer and made them a mediocre manager. And in doing so, you've created two problems where you had none.

This is one of the most common and most expensive mistakes organizations make. Not because the person isn't talented, they are.

But because technical excellence and leadership are different skills, and excellence in one does not predict competence in the other.

The Logic That Gets Organizations Here

The thinking goes like this: they're the best at the work, so they'll be the best at managing people who do the work.

They've earned it. The team respects them.

All three of those things can be true and the promotion can still be wrong.

Managing people who do technical work requires a fundamentally different skill set than doing technical work.

Comfort with ambiguity. Tolerance for others' approaches.

The ability to develop people's capability rather than demonstrate your own. The willingness to let someone do it differently and resist the urge to take it back.

A great technician who becomes a manager often struggles most with that last one. Because the identity shift is harder than the skill shift.

For years, their value proposition, to themselves and to the organization, has been built on being the person who can do the thing better than anyone else.

Now their job is to create the conditions for someone else to do it. That's not a promotion in any meaningful sense. It's a career change wearing the same badge.

What the Framework Says About This

The Half & Half framework identifies Delegation as one of the twenty essential leadership traits — The Multiplier in Limited Time.

The inability to delegate isn't a workflow problem. It's a self-awareness problem.

A leader who can't let go of the technical work hasn't yet separated their identity from their craft. And until they do, they'll always find a reason to take it back.

This is also where Self-Awareness becomes load-bearing.

A leader who understands why they're reaching for the keyboard, who can name the discomfort of watching someone else do it differently and choose not to intervene, is practicing one of the hardest and most underrated leadership skills there is.

The technician-turned-manager who succeeds isn't the one who stops caring about the craft. It's the one who learns to find their satisfaction in what the team produces rather than what they produce themselves. That transition takes time, deliberate development, and a leader above them who creates the space for it.

Most organizations don't build that space. They hand someone a new title and expect the transformation to follow.

What the Research Confirms and Experience Amplifies

The Peter Principle, the idea that people rise to their level of incompetence, was documented in 1969.

Organizations have been proving it in engineering departments ever since.

A 2019 study in the American Economic Review found that the best-performing individual contributors were consistently the most likely to be promoted into management, and that their technical performance before promotion had essentially no predictive value for their effectiveness as managers.

We've known this for decades. We keep doing it anyway. Because it's easier to reward someone with a title than to build a system that doesn't require one.

What to Do Instead

Build two tracks.

One for technical excellence, a path where the best engineers can grow in seniority, compensation, and influence without being pushed into people management.

One for leadership, a path that explicitly develops the skills that management actually requires. Assessment centers, stretch assignments, peer leadership opportunities, formal coaching.

Not a title handed to the highest performer.

Ask the person what they want. Not what they think they should want. Not what the org chart suggests is next. What they actually want. Some of your best technical people will be relieved.

They didn't want to manage anyone. They wanted to keep doing the work, better, deeper, with more autonomy.

The promotion they were about to accept was going to move them further from the work they love and closer to the meetings they hate.

Let them stay. Build the track that makes staying the right choice.

And for the people who do want to lead, who are genuinely drawn to developing others, who find meaning in the team's output rather than their own, invest in them properly.

Not with a title change and a handshake. With the development that the role actually requires.

The Organizational Cost of Getting This Wrong

You lose on both ends. The technical expert, now managing, is less effective as a manager and unavailable as a technical resource.

The team they're managing loses the benefit of strong leadership while gaining the cost of inexperienced management.

And the message sent to every other high performer watching is clear: the only path forward here runs through management, whether you want it or not.

The best talent in technical roles will eventually find organizations that have figured this out. Those organizations exist.

They're the ones where a Principal Engineer earns as much as a Director and carries as much organizational weight. They're not common. They have the pick of the market.

What does your career track say about what this organization actually values? And when did you last ask your best technical people what they actually want?

Delegation and Self-Awareness; two of the twenty traits in Half & Half: Leadership Traits for the Chaotic Center.

The field manual for leaders navigating the space between performance and people.

Available now on Amazon.