#117 - The three Engineering Leadership transitions!
6 Aug 26
Trial Brief
Every Engineer who rises through the ranks eventually discovers the same uncomfortable truth. The skills that got you promoted are not the skills the next role requires. You don't fail because you stop being good at Engineering. Rather you fail because you keep trying to lead the way you have always led. However, the context and operating environment has completely changed.
Trial Execution
I've watched this play out at close range across three decades of a career. I started out as a communications and navigational equipment maintainer on board a nuclear submarine. Promotion to the Officer cadre meant standing back from the role I once had, and watching someone else make the same mistakes I had, letting them learn the way I once had to.
In the Navy we called micromanagement the 'long screwdriver.' As a maintainer, I hated being on the receiving end of it. So I went from the Engineer who wanted to be the one who found the fault, to the leader who had to trust someone else's diagnosis, to eventually the person whose job was no longer to be right about the Engineering at all, but to be right about the conditions the Engineering happened within. Each transition felt less like a promotion and more like being asked to unlearn the exact thing that had made me good at the job before it.
Trial Findings
There isn't one leadership transition in an Engineering career. There are multiple. But of those transitions, three in particular stand out. Most of the struggle we see in Engineering organisations comes from leaders who never consciously made the shift, and are still trying to operate one level down from where they now sit.
Transition One: Individual Contributor β Team Leader
This is the most visible transition, and the one most organisations at least attempt to prepare you for. The Engineer who was closest to the detail, the one who could debug the circuit, trace the fault and fix the kit is now responsible for people who do that for them. The instinct is to micro-manage, to jump into the technical argument and win it or to answer the question rather than ask it. It is your comfort blanket; it's what you're good at.
The real skill here isn't technical anymore, it's letting go of providing the best answer in the room, and becoming the person who gets the best answer out of the room. Most new leaders don't fail this transition through incompetence. They tend to fail it through their reluctance to stop being the smartest person working on the problem.
Transition Two: Team Leader β Leader of Leaders
The second transition is quieter, and far less discussed which is exactly why it catches people out. You're no longer managing work; you're managing the people who manage work. Your old tools; direct oversight, hands-on problem solving, and knowing the detail yourself stop scaling. You now have to lead through other leaders, which means your primary output shifts from decisions to judgement transfer. Your focus must now be on coaching your leaders to make the calls you would have made, without you being in the room.
This is also where ambiguity starts to bite. As an Individual Contributor and even as a first-line leader, most problems still have a right answer, which is backed up by data. However, as a leader of leaders you're increasingly making calls based on incomplete information, against competing priorities and with no clean technical proof of correctness. The confidence that came from being right starts to erode. It has to be replaced by a different kind of confidence: that of gaining comfort in deciding well but without certainty.
Transition Three: Leader of Leaders β Director / Enterprise Leader
The third transition is the least intuitive, because it's the least technical of all three. By now, technical mastery is exactly what you've spent a career building. At this level, your job is no longer to run the Engineering. It's to shape the conditions that the Engineering operates within: strategy, culture, resourcing and, critically, now influence.
Two things change disproportionately at this altitude. First, the grey zone widens further still: strategic decisions rarely have a factually 'correct' answer at all. Here, there are only better and worse bets which must be made under genuine uncertainty. Secondly, you stop being a participant in the business and start being a face of it. The board, customers and the wider organisation are now watching how you carry yourself under pressure. Your presence itself becomes a leadership tool, whether you intend it to be or not.
The Common Thread
Each transition moves you one step further away from the detail, one step deeper into ambiguity and one step closer to leading through influence rather than direct control. That progression is disorienting precisely because it inverts what made you successful in the first place. The Engineers who navigate it well are the ones who consciously ask, at each threshold: what got me here won't get me there...so what do I need to deliberately unlearn?
Trial Sign-off
One practical action
A question worth asking yourself this week, wherever you are on the ladder is:
'In the last month, where did I reach for the old tool i.e. solving it myself, needing the data, wanting certainty...when the role actually needed something else from me?'
Write down one specific instance. That instance is your edge to work on.
One question for reflection
Which of the three transitions are you navigating right now and what's the old habit you're most aware of that you need to let go of?
Have a great week!
Steve
Responses