From “One of the Gang” to a Technical Leader


The Applicable Bytes

Career & Growth, Technical leadership & AI for developers

20 years ago I’ve worked at a car wash to pay my rent. Then as a tech guy I’ve worked as junior, senior, tech lead, managing consultant, principal and now a director of AI, and yes I can confirm it, becoming a manager is hard. But becoming the manager of your “former” peers? That’s a whole different level.

This transition is one of the most uncomfortable transitions in any tech career because boundaries shift, relationships change, and the fear of “messing it up” becomes very real.

(I tried to fix my face with AI, but it was taken with a potato, so this is the best I have...)

I’ve lead about 50 people in different teams on 200 projects, but that was not enough, so I’ve studied two management courses on Harward, and one year on business course in the University in Tromso. Even that was not enough, so I’ve teamed with my friend Husam (LinkedIn) who worked as technical lear for 30 years, he was CEO, head of development, managing director, and all this time a great coach to many. And we want to share our stories.

So now we think we are ready to share our two cents on this topic. We have a lot on our minds, but for now we want to go deeper into how to:

1. Reset expectations without damaging trust

My personal oppinion is that this is most difficult thing, especially if as a tech guy you do not have a strong social circle outside your job. And there is usually someone from your team who is not happy with your career change. When this happens, it might be easiest to work with it, then to fight it. But that takes quite a lot of practice and patience, and honestly few burned bridges.

2. Build authority through actions, not ego

This one is tricky if you are maybe not the most skilled person in the team/company. Imposted syndrome hits hard here, but that is why you need to udnerstand that the good manager is not always (actually is rarely) the best skilled person in the company. Your biggest skill here is to see “bigger picture” and make decisions based on that, not always what is technically best thing to do. And that requires communication. There are few trics in communication and negotiation like mirroring and observations, but the key I think is being prepared for the difficult questions. And constantly checking yourself if decision you made was the right one.

3. Navigate early tension with confidence

Tough one. I personally use humor to brake tension, but that doesn’t work reliably. It requires good relationships in place, which is hard if this is your first leading responsibility. Techniques like labelig and cold read are very effective here, but again, like everything else, this is a muscle that you might not have trained so far. However, starting intentionally might help you A LOT.

4. Balance empathy with accountability

Again a sense of balance is important here, and if you are like 90% of tech dudes or dudetes, empathy is probably not the first thing you write on your CV. We just think more logically, but we do have feelings, and we “feel” that something might not be right decision. And when we do that, we start procrastinating, we start challenging decisions, and we jump to safe choices and do what we know, and what “feels” right, and sometimes even fun. But kids do what is fun, grownups do what is needed for the higher purpose. And you will need to get other grownups, probably smarter then you, to do what is not fun, what they do not believe is the right choice, because it benefits the company or the team at this point. And you need to understand how to connect with people, and still get them to trust you and help you succeed.

But lets talk more, if you are interested to hear out thoughts, please joine a free LIVE lightning lesson: “Leading Peers: A Real Talk from Both Sides of the Table”

Direct link: https://maven.com/p/5f95e2/leading-peers-a-real-talk-from-both-sides-of-the-table​

Just to be transparent, there will be an offer to join the full "do it with you" hands-on live cohort if you are interested. We will probably have a discount cupon available, but this part is completelly optional.

I hope to see you in the Lightning lesson, and let’s make your first leadership step a strong one!

Postboks 60, Bergen, Vestlandet 5821
​Unsubscribe · Preferences​

Dalibor Jovic

I help lonely developers, technical and AI leaders with their career and with AI adoption. Once every few weeks I send an email about AI adoption, good coding practices and personal development.

Read more from Dalibor Jovic

The Applicable Bytes Career & Growth, Technical leadership & AI for developers A few minutes into my conversation with Anders Dræge, I realized something slightly embarrassing. He has won awards for his AI work. The last award I remember winning was for school electronics, somewhere around eighth grade. And the difference between us isn’t the technology. Anders leads AI development at Frende Insurance in Norway. His AI systems run in production, and together they save over 400 human hours a...

The Applicable Bytes Career & Growth, Technical leadership & AI for developers You can have 100 projects of five years of experience in one company, and still not be senior. Because repetition is not the same as growth. That sounds obvious when you read it. It was not obvious when I lived it. After five years of programming, I looked strong, on paper: around 100 projects, a team lead title, and forum administrator credibility from the old PHP days. Those things helped me get my foot in the...

The Applicable Bytes Career & Growth, Technical leadership & AI for developers 20 years have passed since I got paid to code for the first time. Here are few things I’ve learned along the way. Most programmers think a career grows with time. Get a job. Complete projects. Stay long enough. Become senior. I did that. I worked on around 100 projects, became a team lead, moved to Norway, and arrived confident that my experience would open every door. Then I discovered I was a junior developer...