Is anyone else in an infosec leadership position just NOT ready to stop being technical? I've read so many posts about the 'natural progression' from engineer/analyst to leader and I'm a little nauseated by the comments. "You don't need to do that anymore": False. Your team knows when you don't know what you're talking about. Yes, as a leader you should delegate and rely on the expertise of your team, BUT, you really need to know at a base level what your team members are doing so you can effectively prioritize efforts and communicate it up the chain. "You don't have time to dig in": This should be false as well. If you don't have time to devote to keeping skills sharp, I would argue that you're either at the wrong place or you need better time management skills. I guarantee you could trade-in your doom scrolling time and have plenty of time to upskill. "Why would you want to? You made it!": Nauseating. I'm in this line of work because I have an unhealthy obsession with understanding how things work and want to break them / make them better. If you chose security just because it pays well / it's a hot industry, and you don't actually enjoy the work or understand the technical side.. you might be what's wrong with security leadership. This concludes my quarterly rant about my beloved industry.
I'll be technical until the day I die. I'll be in hospice fixing code on my EKG.
I never understood the trend of not understanding the department you are leading... how does that even work? Letting go to the point of not understanding meetings and purchases... come on... Of course the person needs to be technical.
You need to know and understand the tech, but you shouldn't be pushing the buttons or be the one that deals with the technical escalations. If you have to "save the day" with button pushing, you're not the leader, you're the expert. A leader's job is to make sure the team has what they need to succeed. Clear roadblocks. Drive efficiency, metrics, etc... make sure the rest of the company knows your team is doing what it should. The head coach is not out there with the ball, he's orchestrating the team.
Great post and a challenge so many people I speak to face (I posted about it yesterday). It seems that many good people are pushed into management and further and further away from the "tools" as that s the only clear line of progression - but that's not what everyone wants just like yourself. Technical leadership is one of the hardest skills to find in our industry where people can remain technical and "hands on" as well as manage and lead teams. You shouldn't be forced to do one or the other.
Since I am a technical leader who like you - can’t give up the ghost on being technical, I would say that I enjoy certain benefits by being technical but playing it down. You can ask very Socratic lines of questioning for mentees and those in your charge, without solving the issue - allowing them to fully own what they are doing. Even in a role where you are a pure people manager or you are on top of the pyramid of an org, knowing how to use the technical in the current state of technology the team is experiencing to get people over hurdles can really be transforming to a team if used effectively. Personally however - because I want the team to grow and because I am not in their trench, I don’t want to be prescriptive. In short, don’t doubt yourself.
I was not ready to stop being technical then and I still am not now, even though I was told I was a natural people leader. I found a way to do both by helping with DevOps from a leadership perspective and helping with our juniors while still researching/breaking everything I get my hands on from the Cyber Threat Intel side. The days of being in a silo with a clear delineation between technical and leadership are well in the rear view, orgs that are still trying to silo are going to be left behind and lose amazing talent.
I agree. I've been a hands-on leader my entire career in management, and I see no other way to effectively lead my teams. If you don't know, you can't relate. And your relationship with your team(s) are pretty much everything.
I've met a lot of leaders, and the best ones are those who adapt to what their organization truly needs. Sometimes, this means being a technical genius and an inspiring leader. Other times, it's more important to be politically savvy or having an exceptional talent for "selling" ideas to the Board. The notion that leadership is a one-size-fits-all model does a disservice to both leaders and the organizations they serve.