As an engineer who becomes a leader – what is your number one challenge?

As an aside, let's not pollute the language with corporate newspeak such as "leader", when we're speaking about merely managers [1]. A Leader was chosen by people who follow him and helps them achieve a common goal. Whereas a manager was selected by company's owners (often by proxy, i.e. other managers) to oversee their interests. There is no voluntary component present - manager's reports have no choice but to obey him/her or else they lose the job. Also, their goals are not common, but are often rather at odds - e.g. employees want maximum paycheck, managers want to pay as little as possible. Managers and leaders are two completely different creatures.

[1] This one seems fairly recent and I suppose it was coined because the term "manager" was creating a bad taste in the mouths of increasing numbers of people.

My number one challenge is increasing my consistency as a leader. When I was writing software, it was OK/anticipated to "crunch" sometimes. In these scenarios, I'd overwork myself, but, in exchange, a lot of code would get written and the project would come in on-time. My personality/emotional state would suffer a bit from it, but then I'd take some time to recoup/prevent burn-out and all is good.

Now, I feel like the game is played differently. Good leaders are healthy and consistent because that provides a psychological safe space for others to work within. A good leader keeps themselves available enough to act as a shield for their reports. That takes energy. If one fails to budget energy effectively, or generally lacks energy, the veil will become pierced and reports become disenchanted with their leader. Rebuilding that trust costs more energy than it did to lose it - which sparks a vicious cycle.

This has been a pretty tough mental shift for me. My default response whenever a problem gets tough is to "gear down," settle in for a long-haul, and push myself to carry us to the finish line. That's no longer the way to succeed.

When I faced that transition, I had to realize that my role had shifted. Rather than doing things myself (which I was good at), I had to help others do things. This let us get more done. I also had to insulate them from the BS of the business - this was my job to participate and filter as appropriate. This took a little while, and I ended up preferring doing the work myself - so I reverted elsewhere.

For me, it's getting some devs to become team players. Many of them are good at what they do but sometimes they become big blockers to the progress of others in the team.

I try my best to unblock people but you just can't unblock someone's attitude to working. Maybe they just need time to understand, but time is also a luxury our projects do not have.

Getting out of your own way.