Should I move from solo contributor to manager without losing my tech edge?

[Matthew15]

I’ve been offered a promotion to a management role, but I’m honestly worried about the transition from being an individual contributor to leading my former peers. How do you handle the shift in relationships and the new responsibility for team performance without losing the technical edge that got you here in the first place?

[LaylaC]

I got promoted after a few years as an IC. The first three months I didn’t pretend everything stayed the same. I scheduled coffee chats with each peer and asked what would make the transition easier for them. I carved out a weekly office hours block for hands on code reviews and mentoring, but I refused to be the bottleneck on every bug. I limited how much code I touched and started delegating fixes so I could see patterns and guide others. It felt strange at first, but it kept the edge in a different form.

[Luna.W]

I tried to keep doing the things I loved in code, but I found I was swapping real coding time for planning meetings. The trick that helped was treating leadership like a product line: set a small catalog of responsibilities, measure impact with simple metrics, and hand off the rest. After a couple sprints, velocity recovered because people felt ownership more than I felt control.

[Justin75]

It was messy. I tried to mentor in name only and still jumped into fixes, which burned me out. The real move was to explicitly let go of certain chunks of work and be honest about what I could still contribute during review cycles. I learned to praise progress publicly and correct gently in private, which is not easy when you used to be the fastest coder among them.

[Kyle.L]

Is the bottleneck really the team dynamics, or is it about your own leadership style?