Great engineering leaders create leaders
- Gregor Ojstersek from Engineering Leadership <gregorojstersek@substack.com>
- Hidden Recipient <hidden@emailshot.io>
IntroThere is one really important thing to know if you want to grow to lead roles. It's shifting your mindset. From: How can I be the best in my craft? This is an article for paid subscribers, and here is the full index: - I used to believe that being a leader means that you need to be the best at what you do Resources mentioned in the article:
Let’s go straight into it. I used to believe that being a leader means that you need to be the best at what you doThis was especially prominent when I was just starting my career. I thought great leaders are the best engineers, with the most experience in the team/organization, who have all the answers and they are never wrong. I also thought that the best leaders do the most tasks and can handle any task swiftly and easily. The so-called “Hero Engineers” nowadays. You can also read why I am not a fan of heroism in the engineering industry (paid article). Well, the more I grew, the more I saw and realized that this stigma is not correct. As I progressed in my career, I saw that we are all learning all the time, no matter the title, seniority or years of experience. We also all make mistakes. Nobody is perfect. I saw how important is to understand this in the engineering industry where things are changing very fast and if you don’t keep up with learning new things, you start stagnating. Even though I knew that being a leader doesn’t mean you need to be the best and do the most tasks, I’ve made the mistake of trying to be that. And I did that in order to show everyone that I deserve to lead the team and not because of not knowing. I needed to learn this is not the way to go → the hard way. Let’s go to that next. I made the mistake of trying to do everything myself when I first became a Team LeadThis was one of the bad mistakes that I made when I first became a Team Lead. I wanted to be the best engineer, best manager, always energized and always have all the answers. I wanted to mimic what made me a good developer + add additional responsibilities. Well, it didn’t work so well. I was trying to balance leading meetings, having 1:1s, strategy, planning, regularly communicating with stakeholders, etc. and also finish the most tasks as well to show the team why I am worthy to be a Team Lead. Working on the weekends was common for me. On the weekdays, I focused more on being a manager and on the weekends I focused on finishing tasks. It got me close to burning out and I needed to make a change. If I wouldn’t I would probably need a longer break.
You can read my full story of how I became a manager and all the mistakes that I made here: From IC to manager (paid article). These are the changes that made me a LOT better Team Lead and got me promoted to Engineering Manager...Subscribe to Engineering Leadership to unlock the rest.Become a paying subscriber of Engineering Leadership to get access to this post and other subscriber-only content. A subscription gets you:
|
Similar newsletters
There are other similar shared emails that you might be interested in: