The moment most new technical leaders quietly panic is not the first difficult conversation or the first personnel decision. It is the moment they realise they have spent fifteen years getting very good at something that no longer matters as much as it used to.
The promotion happened because you were the best at the work. The problem is that “the work” just changed completely.
Most men in this position try one of two things.
The first is to keep doing the technical work alongside the leadership, staying close to the problems they know how to solve, contributing solutions in meetings, being the smartest person in the room as often as possible. This fails for a specific reason: it signals to the team that you do not trust them, and it builds your authority on a foundation you will eventually need to give up anyway. The second approach is to flip the switch — to decide that leadership is a mindset, read a book or two, adopt the vocabulary, and wait for people to start following. This fails because leadership is a craft, not a mindset. And crafts require specific, repeated, deliberate practice across a set of distinct skills you currently do not have in developed form.
The skills gap is structural — it has nothing to do with intelligence or work ethic. As a technical expert, your value came from knowing more than the people around you and being right more often. You were rewarded, year after year, for individual competence. Every good habit you built pointed inward — toward your own output, your own accuracy, your own problem-solving speed. Now, every one of those habits is mildly working against you. The craft you need runs in the opposite direction.
Here is what closing that gap actually looks like.
The first impression you make as a leader
The first thing to get right is the first impression you make as a leader. New leaders who begin soft rarely recover. This is an argument for clarity, not aggression. In the first week, name your standards explicitly, and apply them to yourself visibly and immediately. If you say you want direct communication, model it in the first team meeting. If you say you value accountability, hold yourself to a commitment publicly within days. The mechanism is straightforward: people are reading your first weeks for evidence of whether the standards are real. Every time you let something slide early, you create a norm that takes months to reverse. Practically, this means identifying two or three specific standards before your first week — punctuality of information, honesty about problems, following through on commitments — and creating visible moments where those standards are demonstrated, not just stated. The aim is to establish credibility fast enough that you can afford warmth later, because warmth without credibility reads as weakness.
Moving from solving to opening
The second shift is the single hardest one: moving from solving to opening. You have been trained to have the answer. The instinct when someone brings you a problem is to solve it — quickly, correctly, with the efficiency that made you good at your job. That instinct will cost you your team’s initiative every time you follow it. When you solve their problems, they stop bringing you their thinking and start bringing you their stuck points. The protocol is simple but uncomfortable: for one month, identify the three conversations per week where your normal move would be to give the answer, and instead ask one question that requires the other person to do the thinking. Not a rhetorical question. An actual question about what they see, what they have tried, what they would do with more authority. Then stay quiet. Track whether, over four to six weeks, people start arriving with more developed proposals. If they do not, the questions were not genuine — they were disguised answers. Adjust.
Build your outward attention as a deliberate practice
Third: build your outward attention as a deliberate practice, not a personality trait. Technical work is internally focused — you think hard, you produce, you refine. People work requires you to catch what other people are not saying. Before every one-on-one or team conversation this week, set a specific intention: your goal is to learn one thing about what this person actually thinks or needs that you did not know going in. Not to update them, not to direct them — to learn something. If you cannot name that thing at the end of the conversation, the conversation was not a leadership conversation, it was a status update. Do this for three weeks. The mechanism here is that trust is built less through what you say and more through evidence that you are genuinely attending. People can feel the difference between someone who is processing them and someone who is actually present.
Earn authority, do not assume it
Fourth: earn authority, do not assume it. The title gives you formal power for about thirty days. After that, it is maintained by whether the people around you believe you are competent and that you are working in their interest, not yours. This is especially true if you were promoted over peers. The practical move is to know the details of your team’s work well enough that your questions are useful rather than generic. Not to do their work — to understand it precisely enough that you are a credible resource rather than a bureaucratic layer. Schedule thirty minutes once a week to sit with one team member and understand what they are actually working through, with no agenda beyond understanding the work. Over three months, you will have covered most of the team, and you will have the kind of operational knowledge that makes your judgment worth something to them.
The honest caveat
The honest caveat: None of this will work if you are also being asked to produce technical output at your previous rate and lead the team simultaneously. The skills gap is real, but the time gap is equally real. If the role has not been structured to actually give you time to lead — to observe, to have genuine one-on-ones, to think about your people — then you are being set up to do two jobs poorly instead of one job well. This framework requires roughly four hours per week of deliberate attention to the craft. If you do not have those four hours, the conversation to have is with your own manager about what the role actually is.
Tomorrow morning, before your first meeting, write down the name of one person on your team and one thing you do not currently know about what they are struggling with in their work. Make that meeting the place where you find out.
