The delivery date is approaching. An executive readout is on the calendar. Your engineering manager has the technical answer, but every decision still routes through them. The roadmap keeps getting rewritten. Team members wait for approval. You find yourself pulled into details that should have been handled two levels below you.
When I hear a director describe a new IT manager struggling, the conversation often starts with the person’s capability. Was the promotion a mistake? Does this manager have enough leadership presence? Can they really operate at the next level?
Those questions may feel practical, but they skip the first one that matters:
Did anyone explain what the job became when the title changed?
The strongest engineer on the team often gets promoted because they are trusted, technically sharp, and already carrying informal influence. Then the organization hands them a management role with a new set of expectations and little operating guidance.
For a while, their technical strength covers the gap. They jump into the hardest problem, rewrite the executive update, make the final call, and rescue a slipping delivery date.
Then the team grows, the portfolio expands, and the manager becomes the person every decision waits on.
That is when a director may conclude, “They aren’t leadership material.” I have seen that conclusion reached before anyone defined the work of leadership clearly enough for the person to perform it.
How to spot a new IT manager struggling before delivery slows
A technical expert can look effective while operating in an unsustainable way. The warning signs usually show up in the team’s patterns before they appear in a performance review.
Watch for these conditions:
- The manager is still the final reviewer for architecture, code, product details, and routine execution questions.
- Team members bring problems upward without a recommendation or a clear decision request.
- The manager gives detailed answers quickly, so the team keeps returning with more questions.
- Cross-functional partners say the manager is difficult to get time with, while the manager says nobody else can represent the work accurately.
- Executive updates contain plenty of technical detail and very little about trade-offs, risk, customer impact, or decisions needed.
- Delivery depends on the manager’s personal effort late at night or during a crisis.
None of this automatically means the manager lacks potential. It may mean the organization continues to reward the old job while expecting performance in the new one.
The shift can be uncomfortable
A strong engineer is trained to reduce uncertainty by understanding the details. That instinct serves the team well when the engineer owns the technical problem. It becomes expensive when the manager’s role is to create clarity through other people.
The shift can be uncomfortable. Their output is no longer primarily a design, system fix, or technical decision. What the team needs from them now is a group that can make sound decisions, communicate risk early, and deliver without waiting for one person to inspect everything.
That work requires delegation, coaching, prioritization, conflict management, and communication with senior stakeholders.
I have seen technical managers hold onto the work they know because the new work feels less concrete. A code review has a visible answer. Feedback conversations carry more uncertainty. When the organization has not made the new expectations explicit, the manager retreats toward technical work because that is where competence feels safest.
This is also where micromanagement can begin. The pattern often starts with care and responsibility, then turns into control. I wrote about that line in Leading Accountability Without Turning Into the Office Police, which covers how the same instinct turns into policing the team.
What the first six months should have included
A new manager needs a deliberate operating agreement. Without one, the person has to guess what matters, how decisions should move, and which behaviors senior leaders will evaluate.
The first six months should have created clarity in six areas.
Start with a job defined by outcomes. The manager should know which team results they own, which decisions belong to them, and what success looks like beyond meeting delivery dates. That may include team health, predictable execution, talent development, stakeholder trust, and early risk communication.
Then reset the technical contribution so their calendar stops looking like the calendar of a senior individual contributor. They may still need enough subject-matter depth to guide the team, but more of their time should go to setting direction, developing people, resolving dependencies, and making trade-offs visible.
Delegation has to be mapped to real work, not treated as a vague leadership virtue. Some architecture decisions can move to a senior engineer. A team lead may be ready to own certain executive updates. You may also find recurring approvals that should be removed entirely.
The role also needs a communication rhythm, a clear format for communicating delivery status, risks, decisions, and support needed. If every update is rewritten by the director, the manager never learns how to communicate at the level the role requires.
A monthly review is too slow when someone is learning a fundamentally different job. Early feedback loops should examine what the manager is spending time on, what decisions are stuck, what the team is waiting for, and where the manager is avoiding necessary conversations.
Visibility with senior leaders should be planned, not reserved for crisis meetings. The manager needs opportunities to present a decision, explain a trade-off, and answer reasonable questions from executives while the director is still close enough to coach afterward.
This support does not require lowering the bar. It gives the person a fair chance to meet the bar.
If your organization skipped this work, do not spend the next quarter pretending the gap will close on its own. The manager is already learning from the signals around them. If you keep stepping in, rewriting, and approving, you are teaching them that leadership means waiting for you.
What to do when the transition is already off track
Start with an operating review, not a label.
Ask the manager to walk through a recent week. Look at where time went, which decisions required their involvement, what they personally completed, and what the team could have owned with clearer direction.
Then compare that reality with the role you expect them to perform.
A useful conversation sounds like this:
“Your technical judgment is still valuable here. The role has expanded, and the team needs more of your leadership work. I am seeing too many decisions, updates, and technical reviews wait on you. Over the next 60 days, we are going to move specific responsibilities to the team, clarify your decision rights, and strengthen how you communicate risk upward.”
Be specific about the work that moves. “Delegate more” is not an operating plan.
Choose two or three recurring responsibilities that are creating the most drag. It might be approving routine production changes, preparing every executive readout, or personally resolving cross-team dependencies. Decide who can take each responsibility, what guardrails apply, and when you will review the results.
You also need to examine your own behavior. Are you asking the manager to own outcomes while keeping approval rights for every meaningful decision? Do you request detailed updates because the manager has not built trust, then prevent them from building trust by rewriting every update yourself?
Your manager may need direct coaching on delegation, feedback, prioritization, or executive communication. They may also need a clearer role design. If the team has grown substantially while the manager still carries a large individual-contributor workload, more coaching alone will not solve the capacity problem.
The earlier post, Before You Buy Leadership Training, Know Which Problem You Have, can help you separate a skill gap from a role-design or environment problem. A workshop can support a skill gap. It cannot repair impossible workload, unclear authority, or conflicting priorities.
Give technical managers visibility without throwing them into the deep end
Senior leaders need to see the manager operating at the next level. The manager also needs a safe enough runway to practice before the stakes are high.
Start by choosing the right moments.
A routine executive readout can be useful if the manager owns a clear section and understands what the audience needs. Give them the business context behind the meeting. What decision is being considered? Which risk matters to the executive team? How much detail belongs in backup material?
Before the meeting, ask the manager to prepare three points, what is happening, why it matters, and what decision, trade-off, or support is needed. That structure keeps the conversation out of the weeds.
Coaching, not hijacking
I know what it feels like to be on the receiving end. In a meeting, I was asked directly, “Kellye, what are the key deliverables of this project?” I got one word out before a senior leader jumped in with their answer. I was hijacked, and it did not feel good.
During the meeting, resist the urge to answer the first difficult question. Give the manager room to think. If you need to add context, build on their answer instead of taking over. Afterward, debrief the moment. Which answer built confidence? Where did the manager over-explain? This is where a lot of directors realize they either coached the moment or took it from the manager.
You can also give the manager ownership of a cross-functional decision, a planning segment, or a short update during a leadership staff meeting. The assignment should be real.
Pay attention to whether the manager can explain trade-offs in language that product, finance, security, and executive partners understand. Technical credibility matters, but senior leadership also needs to see judgment, prioritization, and the ability to keep a team moving when every option has a cost.
If decisions are still drifting upward, review the boundaries. Why Every Decision in Your Org Ends Up on Your Desk offers a practical look at how unclear authority creates a decision bottleneck.
A director can also pass along my Find My Leadership Gaps quiz to a manager who needs a starting point for self-reflection. Use it as a conversation opener, not as a substitute for direct feedback.
Decide whether the person needs support, redesign, or a different role
After you clarify expectations and provide support, watch the pattern of behavior.
Look for signs that technical control is starting to loosen and that decisions are moving closer to the work. Team members should also be becoming more capable and visible, with communication to senior leaders getting clearer.
You are looking for movement, not perfection.
If the manager continues to avoid people leadership, refuses to delegate, or treats every question as a technical problem to solve personally, you have useful information. So do persistent delivery issues, unclear communication, and a team that remains dependent on one person.
At that point, the decision may involve role design, additional development, or a different career path. Technical expertise remains valuable even when people management is not the right assignment.
A new manager’s first six months shape more than that person’s career. They shape whether the team learns to operate with judgment, whether senior leaders trust the layer below them, and whether you can spend your time on the work only you can do.
If you are planning a 2027 chapter meeting, leadership retreat, or professional development day, Kellye’s signature talk, “Why Technical Leaders Stall at the Middle Management Level,” gives your audience a direct look at this transition and the leadership behaviors required next. Learn more on Kellye’s speaking page.
If the pattern is affecting more than one leader, the Leadership Performance Diagnostic can identify where leadership performance is getting stuck and what to address first.
