The hardest lesson I learned as a tech lead wasn't about architecture or code quality. It was about knowing when to step back.
Early in my career, I reviewed every pull request, attended every standup, and had an opinion on every decision. I thought that was leadership. It wasn't. It was a bottleneck wearing a leadership badge.
The shift happened when I started asking myself one question before jumping in: "Will this team be stronger if I stay out of this?"
Most of the time, the answer was yes.
When you stop being the person who approves everything, something interesting happens. People start owning their decisions. They debate more thoughtfully because the outcome is genuinely theirs. They grow faster because they're not waiting for permission.
The best engineering managers I know have mastered the art of strategic absence. They're not checked out. They're deliberately creating space for their team to step up.
It feels counterintuitive. Leadership as subtraction. But the teams that scaled best under me were the ones where I made myself progressively less essential.
Your job as a leader isn't to be needed. It's to build something that doesn't need you.