Once you move in to manager role- people are your product not technology.
Based on how the teams are structured, your roles and responsibilities will be different.
In some organisations the teams may be smaller and you may write code, however in other organisations you may just do the people leadership, process and governance. In some other orgnaisation you may ask to do the coding + people leadership, process and governance.
In the end, Your job description may be totally different and your measurement of success will not be the same compared with an developer role.
Also to note, not every company puts managers completely away from the tech side. In my current role, apart from leading the people, managing the processes, I work with the project teams to make sure that projects are staffed correctly, and overall technical governance of the project.
It’s hard for great engineers to move into management because they like being deeply focused on challenging technical problems, not hopping in and out of a dozen meetings every day.
You have to enable your team for success and trust in them to deliver, instead you are doing the actual work. Let the team do the work and support them where needed.
If you want to become a manager, be prepared to give up some of the things you enjoy most about your current role. As a developer, you have a lot of control over your work. But as a manager, you'll have to delegate tasks and manage people, which can be more challenging.
It's important to be aware of some the trade-offs before making the decision to move into management
“Me” time: As an engineer you have your own time to work, as soon as you turn into manager you calendar gets filled up so quickly. You will be hopping in and out of the meeting whole day long. So there will be no "me" time after all.
Effort un-recognized: You will be leading and empowering your team to create long term gains, which most of the times unrecognized unlike an engineer. You are the backbone to the team which never show your face. “Success” is also a lot murkier as a manager which means no praises.
Dealing with people issues: Have you ever worked on an improvement plan to uplift an underperforming colleague. Well, that will be you this time. As an individual contributor, you might think it would be easy to fire a colleague who is not pulling their weight. However, as a manager, you know that it is a difficult and unpleasant task. You have to have the difficult conversation with the employee, and you also have to deal with the fallout from the decision. Having difficult conversation is a huge part of being a manager.
Making technical decisions: When an engineer moves into manager role, they will still hold the technical character to their heart. This will hurt them and the team dearly. Let the team make the decision even you are a ‘Guru’ in that.
Learning new technical skills: As an engineering manager, you may not be involved in day-to-day hands on works, however you should see the broader technology trends in your industry and understand the tradeoffs of different solutions. When you walk-in to a meeting or introduced to a new project then at least you know what’s all about.
No comments:
Post a Comment