I first started managing people when I was 26. Four years later, I was managing a team of 30 developers. On paper, I was fantastically successful; in reality I should have fired myself.
At the time, I thought that in order to lead a team of awesome developers, I had to be an even more awesome developer. I worked frantically to write more code than anyone else not realizing that I accepted a new job the moment I was promoted – and writing code wasn’t it.
It’s something that almost all new managers forget. Being a manager isn’t a glorified version of your old job: it’s a brand new and completely different role. It requires a different skill set and attitude. As a manager, your responsibility is to ensure your team works on the right things at the right pace to deliver the right outcomes.
In my 30s, without any management or leadership training under my belt, I didn’t have a clue how to direct such a sizeable team. As a newbie manager I made mistakes and added further complexity to an already chaotic organization. It was only years later when I truly realized how my lack of leadership contributed to the chaos. I still cringe thinking about it.
I’m not proud of those mistakes, but I learned a lot from them. My biggest takeaway was that being a manager isn’t about rolling up your sleeves and working alongside your team (although there are times when this matters); it’s about understanding where your organization wants to go and deploying your team and resources to get you there.
If you’re a new manager who’s still doing the same work as before, step back and delegate. And, congratulations on your new job.