How can i lead a team and keep my technical edge after a promotion?

[Joseph.A]

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 metrics without losing the technical edge that got you here?

[SophiaFD]

Congrats. I was there a couple of years ago. I started with listening first, not leading with a plan. I did one on ones with each peer for about 20 minutes, set expectations about what ownership looks like, and framed success as team outcomes rather than who ships what. We kept a lightweight dashboard: cycle time, a few critical defects, and a quick health check after each sprint. I still did a little hands on work, but only on things that needed a technical nudge rather than full ownership, and I used code reviews as my way to stay close to the craft.

[AbigailQR]

I tried to stay technical by taking on a tiny feature here and there, but once you’re managing people, half your day vanishes in meetings. I ended up skimming PRs and answering questions instead of diving deep. The depth I used to have never fully returned, and the code review turnaround slipped from a day to several days.

[EthanM]

Maybe the real issue isn’t the shift in relationships but whether the team has clear, shared goals. Are you sure you have a crisp definition of what success looks like for the squad, or is it still about proving you can code and not about leading?

[Andrew_M]

One memory that stuck: I overheard a coder venting at the coffee machine and realized morale is visible in small moments, not slide decks. I tried to chase that vibe while keeping the metrics honest, and I still asked for weekly feedback even when I didn’t know the exact right move.