A growing engineering team can change a manager’s job before anyone changes the expectations that come with it. Code reviews, technical decisions and delivery questions still need answers. Meanwhile, more direct reports need feedback, support and room to develop their own judgment. Keeping every responsibility can leave a manager stretched across work that increasingly competes for the same hours.
Deciding what to give up is difficult when technical involvement helped establish your credibility in the first place. But a larger team calls for deliberate choices about who owns the work, who can make decisions and when the manager needs to step in. The challenge is to preserve accountability while creating enough space for other people to lead - and enough time to do the management work the team now needs.
Identify Where the Team Is Waiting on You
A full calendar can tell you that you’re busy. A closer look reveals which responsibilities belong on someone else’s calendar.
Jason Long, founder and CEO of SupportMy.Website, tells Dice that his team grew from five to fourteen direct reports before expanding into multiple teams. That growth prompted him to begin delegating work, including standups, code reviews, sprint grooming, and daily triage.
“I tracked my time for six weeks. Two thirds of it was tactical work a lead could be doing,” Long says. His account offers a concrete starting point for a manager whose scope has expanded: examine where time goes before proposing changes. Identify recurring work that requires your involvement, then consider whether another person could own it with the right context and support.
Rehan Ahmed, CEO of Smart Web Agency, encountered a similar problem as his team grew. “The biggest sign was that too many people were waiting for my answer. That slows delivery and does not help people grow,” Ahmed tells Dice.
Ahmed handled technical decisions, delivery, client discussions, and developer support. As the team grew, he transferred day-to-day responsibility to project managers and technical leads, concentrating instead on larger decisions, client relationships, team structure, and removing blockers.
For engineering managers, those experiences suggest two useful questions: Which responsibilities consume time that someone else could use more effectively, and where does waiting for your involvement delay someone else? The answers can help you distinguish work you need to keep from work you’ve kept doing out of habit.
Give People Authority Along With Responsibility
Transferring a task raises another question: Who has the authority to decide when the work is ready or which approach the team should take?
Long made that boundary explicit when he handed work to his lead developer. “For instance, I handed off daily standups and code reviews to our lead developer,” Long notes. “It’s an engineer I trust and know is strong technically. It was important that I made it known to the rest of the team that he is the last word when it comes to the majority of our day-to-day technical decisions.”
Ahmed describes a similar separation of responsibilities: “We now have clearer ownership: technical leads handle technical decisions, project managers handle delivery, and issues come to me when they genuinely need senior direction.”
Both accounts put ownership in terms the team can act on. The person receiving the work knows which decisions they can make, and colleagues know where to take questions.
A related transition occurred for Alex Donovan, founder of web design and branding company (a)squaredstudio. His experience centers on creative work and client delivery, where he moved away from producing designs himself and toward leading the people producing them.
“I stopped drawing logos and started looking at logos created by my team. My mornings changed dramatically, as it was team interaction now and not files,” Donovan tells Dice. Donovan says a trusted designer took over design work, a coordinator assumed responsibility for project timelines, and the team began leading regular client calls. His account shows how a change in ownership can change what a manager does day to day. The conversation shifts toward the people doing the work and the support they need to deliver it.
Allow Room for Decisions You Wouldn’t Make
Delegating work also means encountering choices that differ from your own. That can test whether you’re comfortable with the authority you’ve given someone.
Donovan describes that tension after handing leadership of the design work to his most senior designer. “Some of the time their decisions have been better than mine, some of the time they’ve been worse. Overall quality of work hasn’t suffered but our voice has wavered a bit,” Donovan says. He says he hasn't stepped in simply because a choice differed from what he would have done, though he retains final approval over work going out under the studio’s name.
For an engineering manager, the useful question is what would justify intervention. A disagreement over implementation preferences may warrant a different response from a decision that conflicts with an agreed architectural constraint. Establishing those boundaries gives a lead a clearer basis for exercising judgment and a manager a clearer reason to intervene.
Ahmed identifies another cost of stepping back: reduced visibility. “The trade-off is that you lose some visibility into every small detail. But if you keep holding every decision yourself, the business cannot scale. The important thing is regular communication, clear accountability and giving people the authority to make decisions, not just more tasks,” Ahmed says.
Agreeing on what to communicate can make that trade-off manageable. A manager might ask for updates on unresolved risks or decisions affecting other teams, while leaving routine choices with the lead. The aim is to stay informed enough to provide support without making every update another request for permission.
Make Role Changes Specific Enough to Evaluate
A proposal to change your responsibilities needs to account for the work you leave behind and the work you intend to give more attention to.
Long describes putting that proposal into concrete terms. “When it came down to it I laid out what work I wanted to give up, who would pick it up, and how we would determine if it had been successful after 90 days,” Long says.
For a manager discussing scope with a director, that structure makes the conversation actionable. Identify the responsibility being transferred, the person taking it on, and the support they will need. Explain how the change would create room for responsibilities such as coaching, planning, or resolving issues across teams.
The review should examine whether the new arrangement serves those purposes. Depending on the problem, useful measures could include decisions awaiting approval, delivery commitments, or protected time for employee development. Include the new owner’s perspective: taking responsibility may reveal gaps in authority, information, or preparation that need attention.
Conclusion
Delegation becomes meaningful when someone else can exercise judgment within an understood boundary. That may leave a manager with less visibility into routine work and less control over individual choices. It also creates an opportunity to develop people who can take greater responsibility for the team’s work.
As your team grows, make that transition intentional. Agree on what others can own, what still requires your involvement, and what you will do with the time the change creates. A revised role should leave you better able to support the team - and leave the team better able to move work forward without waiting for you.
