You were good. Really good. So good that you got promoted. From the best developer to team lead. From the most successful project manager to department head. From subject-matter expert to group lead. And now, at times, you feel like an impostor. <\/p>\n\n
The work you have been rewarded for so far is now your biggest obstacle. Instead of solving problems, you are expected to \u201clead.\u201d You sit in meetings that have nothing to do with your expertise. You mediate conflicts between people you like. You make decisions on topics you understand less well than your employees. <\/p>\n\n
\nThe skills that made you a manager are not the skills that will make you successful as a manager. This is not a criticism of you. It is a structural reality that affects almost every new manager. <\/strong><\/p>\n<\/blockquote>\n\n
A team lead I supported in her first year put it perfectly: \u201cI was the best in my field. Now I\u2019m the worst at my new job. And the worst part is: nobody told me this is normal.\u201d It is normal. And it is predictable. Three pitfalls show up in the first year with a regularity that is almost comforting.<\/p>\n\n
You remain the top expert<\/h2>\n\n
The first and most common mistake: you keep doing what you are good at. As an expert, your value was your personal performance. The quality of your code. The precision of your analyses. As a manager, your value is your team\u2019s performance. No more, no less. <\/p>\n\n
But old habits die hard. You spot a bug in the code and fix it yourself instead of addressing it. You receive a complex request and handle it yourself because it is faster. You sit in a meeting and answer the technical question yourself before your employee can even speak. <\/p>\n\n
Every time you do that, three things happen. You signal to your team that you do not trust them. You prevent your team from growing, because people learn through challenges and you remove every challenge. And you make yourself indispensable in the wrong way\u2014not as a manager who builds a strong team, but as the expert without whom nothing works. <\/p>\n\n
80% quality that scales beats 100% quality that fails at the bottleneck. And that bottleneck is you. Learning to let go<\/a> feels like losing control at first. Like a loss of quality. Like inefficiency. But it is the only way you can scale as a manager. Your personal output has a ceiling. Your team\u2019s output does not. <\/p>\n\n
The identity crisis nobody talks about<\/h2>\n\n
What is rarely discussed: the transition to manager is not just a skills issue. It is an identity crisis. <\/p>\n\n
As an expert, you knew who you were. Your self-worth came from your knowledge, your problem-solving ability, your professional excellence. \u201cI\u2019m the best developer on the team.\u201d \u201cI\u2019m the one who solves every problem.\u201d That was not just your job. That was you.<\/p>\n\n
And now you are not supposed to use that part of yourself anymore\u2014at least not the way you used to. What remains if you are no longer allowed to be the expert? Who are you then? <\/p>\n\n
Marshall Goldsmith summed up this dynamic in one sentence: \u201cWhat got you here won’t get you there.\u201d The strengths that got you into a leadership role become the weaknesses that make you fail there\u2014unless you consciously let go of them. New managers compensate for uncertainty by working harder, controlling more, and proving to themselves that they are still the top expert. In doing so, they sabotage the very leadership role they should be growing into.<\/p>\n\n
You have to let go of part of your professional identity in order to build a new one. This is not failure. This is growth. But it often does not feel that way. <\/p>\n\n