I went through what you're experiencing. Stick with it! It's a normal experience for new managers transitioning from sole-contributor. Never do the work of you

I went through what you're experiencing. Stick with it! It's a normal experience for new managers transitioning from sole-contributor. Never do the work of your team. You have to let them succeed and/or fail on their own. You should set them up to succeed, but don't do their work. Draw clear boundaries, such as you might set requirements or dictate certain architectural details, but be sure that you don't get involved in any implementation-time decisions. This helps guarantee that you won't ultimately be involved in future fixes and re-work. If your team fails, it's not your fault! It's only your fault if you take no corrective managerial action (such as hiring, firing, or changing the way you plan/manage things). Also stay on top of work as it progresses. Ask people how they're doing. Ask for demos and explanations. Set good deadlines. Communicate your realistic (conservative) expectations to your managers, but set ambitious deadlines for your workers. Create actionable plans everyone on the team is accountable to. Identify leaders. If you're the manager, find someone under you to be a lead developer. If your team ends up asking you technical implementation questions, redirect them to your lead dev. Hold regular hours. Don't be available 24/7 for every problem that arises. Make your team self-sufficient and productive without you constantly around. Be very careful hiring. Unproductive devs bring the whole team down by constantly failing and creating extra work for others. Fire people who make the team worse.