I'm going to assume you'll be directly managing the team vs some sort of leveled up developer, but still an individual contributor...
You're now a bonus multiplier. Your individual contributions are less relevant (ie. LOC, etc.) and your focus is on increasing the over all output of the team as a whole. This means getting them the tools/info they need to be as productive as possible and removing all the roadblocks.
It means doing more code reviews and asking the team to stay on top of code reviews in general.
It means listening to the team, even giving one of them "project lead" status, but reserving the [not often used] ability to mandate a decision.
It means regular 1:1 meetings and asking for pointed feedback. Don't ask "Is there anything I can do to make your life better?" ask "Tell me one thing I can do to make your life better." Same question, but the latter shows you really do want that feedback.
Ensure praise goes to the team and blame goes to you (whether or not it's deserved). "The team did a great job delivering this feature" and "I missed this acceptance criteria which is why the feature was late."
I find it really helps me get over the "I'm not pushing code. Gah!" mentality.
Oh, the other thing... don't take tickets that will block the team if you don't get them done ASAP. Cause you'll get pulled into all kinds of meetings and a ticket that would take 1/2 day will take 2-3.
Focused on creating wonderful user experiences by attending to folks needs with empathy and creating spaces of safety. Senior Frontend Developer/Tech Lead at Dolittle.
I'm going to assume you'll be directly managing the team vs some sort of leveled up developer, but still an individual contributor...
You're now a bonus multiplier. Your individual contributions are less relevant (ie. LOC, etc.) and your focus is on increasing the over all output of the team as a whole. This means getting them the tools/info they need to be as productive as possible and removing all the roadblocks.
It means doing more code reviews and asking the team to stay on top of code reviews in general.
It means listening to the team, even giving one of them "project lead" status, but reserving the [not often used] ability to mandate a decision.
It means regular 1:1 meetings and asking for pointed feedback. Don't ask "Is there anything I can do to make your life better?" ask "Tell me one thing I can do to make your life better." Same question, but the latter shows you really do want that feedback.
Ensure praise goes to the team and blame goes to you (whether or not it's deserved). "The team did a great job delivering this feature" and "I missed this acceptance criteria which is why the feature was late."
And a bunch of other stuff too :)
Great answer! I love the idea of being a Bonus Multiplier!
I find it really helps me get over the "I'm not pushing code. Gah!" mentality.
Oh, the other thing... don't take tickets that will block the team if you don't get them done ASAP. Cause you'll get pulled into all kinds of meetings and a ticket that would take 1/2 day will take 2-3.
This is a good one, and something I struggled with personally. Blocking the team because you can’t get work done is just not OK (over time).
There’s a challenge though. It’s easier to then lose contact with the codebase and state of things.
Do you have any recommendations to avoid this?
Not any super good ones no :)
Do more code reviews. It's not quite the same, but at least you'll see the new code that's going into the app.
Chip away at ancillary things, nice to haves, things that won't block anyone, but still keep you somewhat close.
Take a tricky bug now and then. The code snooping you have to do to fix it will get you back into things.