Moving a strong technician into management without training, transition time, or role clarity creates one unsupported manager and one weakened operation.

Most organizations celebrate a promotion as though the hard part is over.

The announcement goes out. Congratulations appear in the chat. Somebody updates the org chart.

Then Monday arrives.

The new manager still owns half the technical workload, has six former peers asking for decisions, and is expected to conduct performance conversations they have never seen done well. Their onboarding often consists of a calendar invitation titled “Leadership Essentials” three months from now.

We promoted them because they were excellent at the old job. Then we quietly assumed excellence would follow them into a completely different one.

A promotion changes the title immediately. Capability takes longer.

When the strongest engineer leaves—but never really leaves

Imagine a Network Operations team whose manager resigns. The strongest senior engineer is promoted. She knows the environment, earns customer trust, and can diagnose a routing problem before most people finish saying “packet loss.”

But nobody backfills her engineering duties. She still handles critical incidents because the team depends on her. At the same time, she must approve changes, coach two struggling employees, manage on-call coverage, report service performance, and handle escalations from a demanding customer.

Within six weeks, one-to-ones are repeatedly cancelled. Change approvals wait while she troubleshoots incidents. Engineers stop raising development concerns because every conversation becomes operational. A recurring network fault remains open because immediate outages keep winning.

Employees lose coaching and clarity. Service delivery becomes dependent on one exhausted person. Customers see slower decisions and repeat incidents. The organization pays overtime, delays succession, and risks losing the very person it just promoted.

The promotion did not fail. The transition was never designed.

When a new manager keeps doing the old job, both jobs become part-time.

Expertise does not transfer by osmosis

Technical work and management overlap, but they reward different habits. A strong technician is often valued for solving problems directly. A manager must create the conditions for other people to solve them.

That shift can feel uncomfortable. Stepping in produces an immediate sense of progress. Coaching takes longer, and the result belongs to someone else. Under pressure, people tend to return to familiar behaviours—especially behaviours that previously earned recognition.

That is not a diagnosis or a failure of character. It is a predictable transition problem. New skills need practice, feedback, and enough space for the person to stop relying on the identity that made them successful before.

Design the transition, not just the announcement

Before the promotion takes effect, leaders should decide which old responsibilities will stop, who will inherit them, and what authority the new manager actually has. A 30-, 60-, and 90-day transition should include real management work: setting expectations, coaching performance, handling conflict, prioritizing demand, and communicating with customers.

Give the new manager a coach who is not their evaluator. Protect time for one-to-ones and reflection. Review decisions without turning every imperfect outcome into evidence that the promotion was a mistake.

And prepare the team. Former peers need clarity about the changed relationship, not an awkward group announcement followed by everyone pretending nothing has changed.

Promote for potential. Transition for success.

Key Takeaways

  • Remove or reassign the old job.
  • Clarify authority before problems arrive.
  • Build a practical 30-60-90 day transition.
  • Coach management skills through real situations.
  • Prepare former peers for the relationship change.

Discussion question: When someone becomes a manager in your organization, what work is deliberately removed so they can learn to lead?