There is a version of the new IT leader that looks incredibly productive from the outside. They are in early and out late. Their calendar is full. Their hands are in everything. If you ask them how things are going they will tell you they are slammed.
What they will not tell you is that most of what they are doing is not their job anymore.
This is one of the most common patterns I see in IT leaders who are earlier in their journey. They got promoted because they were excellent at the technical work. They knew the systems, understood the complexity, and could be trusted to get things done right. That competence is exactly what earned them the role.
And it is exactly what is holding them back from doing it well.
The transition from individual contributor to IT leader is one of the hardest shifts in a technical career. Not because the new leader lacks ability, but because everything that made them successful before now pulls them in the wrong direction. The instinct to dive in and fix things yourself. The discomfort of watching someone else do a task slower or differently than you would. The quiet fear that if you let go of the technical work, people will stop seeing you as valuable.
So they stay busy. They keep doing. And the team never quite gets the leadership it needs because the leader is too occupied being a very capable technician.
I want to be clear about something before we go further. This is not a character flaw. The reason most new IT leaders hold on to individual contributor tasks is not arrogance or a desire for control. It is risk management driven by genuine care. They know what goes wrong when a critical system is handled incorrectly. They have seen the downtime. They have been the one called at midnight. Letting someone else touch something they have spent years mastering feels genuinely dangerous.
What they have forgotten is that at some point, they were the person who had to touch it for the first time too.
Someone gave them that opportunity. Someone accepted the risk of their learning curve. Someone let them make the mistake, helped them understand why it happened, and trusted them to do better next time. That experience is how they became the person who now knows the system better than anyone else in the room.
Delegation is not abandonment. It is the same investment that was made in you, paid forward to the people on your team.
I worked with an IT leader who was new to his company and frustrated that his team was not moving at his pace. He was pushing hard and they were not keeping up. From his perspective they were slow. From their perspective they had a new leader who was flooring the gas pedal without understanding that the car was still warming up.
When we talked through what was actually happening, the shift for him was not a new strategy. It was recognition. He could see for the first time that his push for speed was working against the trust he needed to build first. He started meeting his team where they were, bringing them along at a pace that stretched them without breaking them. Six months later his team was moving faster than he had originally demanded. Not because he pushed harder, but because he led differently.
There is a line I shared on LinkedIn recently that keeps coming up in conversations with IT leaders at this stage. Managing technology and leading technology are not the same job. Managers keep the lights on. Leaders make the business understand why the lights matter.
The new IT leader who is still doing the technical work is managing. The moment they start developing the people around them, building relationships across the organization, and translating technology into business outcomes is the moment they start leading.
That shift creates something they have not had in a while. TIME. Time for the strategic conversations that move the organization forward. Time to develop the skills of the people on their team. Time to build the relationships with peers and executives that determine whether IT has a seat at the table or just a help desk ticket queue.
The team grows because they are trusted with real work. The leader grows because they finally have the space to lead.
If you are in this transition right now and you are too busy, it is worth asking yourself one honest question. Are you busy because the role demands it, or because letting go feels harder than staying in control?
Both answers are valid. Only one of them moves you forward.
Reflection for this issue:
What is one task or responsibility you are still holding onto that belongs to someone on your team? What would it take to hand it over and what would you do with the time it frees up?
If someone forwarded this to you and you would like to subscribe, visit thecandidwalk.com.