4 ms·
I think your first step is to delegate some of your responsibilities ASAP. If you stop writing code and building estimates (but keep doing code reviews!) and ha
by joshyeager 10y ago
I think your first step is to delegate some of your responsibilities ASAP. If you stop writing code and building estimates (but keep doing code reviews!) and hand off parts of the new hire training, that will free up time for other responsibilities. It will also help the people on your team grow so they can carry even more of the load for you.
The Manager Tools podcasts have a lot of very useful advice that I think would help you. I recommend subscribing to their "Basics" feed to get started, and then listen to the full feed. http://www.manager-tools.com/podcasts/basics-rss.xml http://www.manager-tools.com/podcasts/basics-rss.xml
You can see their whole "map of the podcast" here: https://www.manager-tools.com/map-universe/trinity-one-ones https://www.manager-tools.com/map-universe/trinity-one-ones. It's overwhelming at first because they have almost 1000 casts. But you can navigate through the list to find the topic you're struggling with, and download the podcasts from there.
- lojack 10y agoAdditionally, if they're giving the resources for a large team, you may be in a position to hire someone who some of these duties can be delegated to.
- tootie 10y agoI've found that having coding responsibilities is almost detrimental because I never have time to complete them. If I take a dev story off the backlog, it tends to stay open forever because I'm too busy doing managery things. I'll bite off really small bits that I know I can do quickly to at least keep my skin in the game.
- joshyeager 10y agoYes, that is what I've found too.