Why Technical Excellence Alone Doesn’t Create Effective Managers

The pattern is almost universal in technology organisations. Someone excels as an individual contributor — produces great work, solves hard problems, earns the trust of the team. So they get promoted into management. Six months later, the team is frustrated, the new manager is overwhelmed, and no one is quite sure what went wrong.

Nothing went wrong. The organisation mistook technical excellence for management readiness. These are two fundamentally different things — and conflating them is one of the most expensive and preventable mistakes in people management.

The skills that earn the role

As an individual contributor, your value is measurable and direct. You write the code, design the product, build the system. Your effectiveness is visible. Feedback is fast: it works or it doesn’t. The criteria for promotion mirror your individual success. You were the best at the thing, so you got the role.

This logic is rational. It’s also incomplete.

The skills the role actually requires

As a manager, almost nothing that made you effective before applies in the same way. You no longer produce the primary output — you enable others to produce it. Your job is to set context, remove obstacles, build capability, and hold accountability. You succeed when others succeed.

The hardest shift is communication. As an IC, communication is a means to an end: you explain your work, participate in discussions, escalate when needed. As a manager, communication –– how you run your one-on-ones, how you give feedback, how you communicate expectations, how you handle conflict –– is the work. Not a soft layer on top of your real job. The real job itself.

Three failure patterns that repeat everywhere

‘The contributor in disguise.’ The manager keeps doing their old job. They step in to solve technical problems their team should be solving. They’re comfortable there. The team stops developing, because the manager keeps doing the hard parts for them.

‘The feedback avoider.’ Delivering honest, clear, direct feedback requires confidence and communication skill most people haven’t been trained for. So managers default to vague positivity or passive correction. Team members don’t know where they stand. Performance problems compound quietly until they’re impossible to ignore.

‘The context withholder.’ The manager knows why decisions were made, what the strategy is, what the pressures are. But they don’t communicate it downward. The team operates with incomplete information, makes misaligned decisions, and loses confidence in the direction.

What organisations can do

Promoting strong ICs into management without development isn’t just a missed opportunity — it’s a retention risk. The manager is set up to struggle. Their team experiences weak leadership. Both suffer.

Effective manager development isn’t about giving people frameworks to memorise. It’s about changing how they communicate, how they hold accountability, and how they understand their new role. That takes deliberate practice, real feedback, and time.

The technical expertise that earned them the role doesn’t disappear — and when paired with genuine management capability, it’s a significant asset. The problem is when organisations assume the combination happens automatically.

It doesn’t. That’s what development is for.