Building Technical Excellence Through Others
Do these late-night worries sound familiar?
"I want to solve this problem myself because I know I can do it faster, but my team needs to develop these skills..."
"The deadline is approaching, and I'm accountable for delivery, but I can't write the code myself..."
"I know exactly how to fix this bug in five minutes, but I need to let them do it (struggle through it)..."
These are. some of the worries that keep engineering managers awake at night. In my coaching practice, I hear flavours of these concerns—the struggle between responsibility and restraint, between technical expertise and team empowerment. I've observed a profound paradox that Engineering Managers face. The technical excellence that earned them their leadership position is no longer how they deliver value. Instead, their impact now flows through others—a transition that can feel like losing part of their identity.
This shift creates one of the most challenging aspects of becoming an engineering manager - How do we build technical excellence when we're no longer the ones writing the code?
The Invisible Pull of the Gold-Gilded Cage
Remember our discussions about the gold-gilded cage? That invisible constraint where greatest strengths become barriers to growth? This is where it manifests most powerfully for engineering leaders.
Their deep technical knowledge that made them the go-to person now keeps them doing rather than enabling. Their reputation for solving complex problems prevents team members from growing through their own struggles. Their high standards become a ceiling limiting their team's autonomy.
In a recent conversation with an EM she said, "I know I should let my team solve problems themselves, but when I see them taking a path I wouldn't choose, I panic. What if they fail? What if it takes twice as long?"
Sound familiar?
The Hidden Internal Struggle
What many engineering leaders don't talk about openly is how physically and emotionally taxing this restraint can be. On the outside, they appear patient, thoughtful, and supportive as they watch their team work through problems. But internally it's a different story entirely.
One engineering manager I coached described it as ..."I have to physically stop myself from interrupting. I'm nodding encouragingly while a voice in my head is screaming 'just let me do it!'" (Paraphrased)
This internal tension creates stress. The pressure can build up physically (shoulders tense, jaw clenched). The frustration of seeing "the obvious solution" go unnoticed can feel almost painful. And perhaps hardest of all is maintaining that calm, supportive exterior while feeling anything but calm inside.
The technical expertise that formed your professional identity for years doesn't simply go quiet when you step into leadership. It continues to analyze, solve, and critique—now with the added complication that you can't always act on those instincts. This cognitive dissonance between what you know and what you must do (or rather, not do) creates a unique form of leadership stress that rarely gets acknowledged.
A New Definition of Technical Excellence
Building technical excellence through others requires redefining excellence itself. Success becomes measured not by the code leaders write, but by what their team delivers without them—while managing the emotional journey this transition demands.
This paradigm shift transforms leaders:
From problem-solvers to teachers/ mentors of problem-solving methods
From answer-providers to question-askers
From mistake-preventers to creators of safe learning environments
From technical doers to technical coaches
Practical Steps to Letting Go While Levelling Up
Here are some strategies that leaders I've worked with have found useful, many of which align with Agile practices -
Create learning loops, not safety nets. "What worked? What would you change? What did you learn?" This transforms mistakes from things to prevent into valuable learning opportunities.
Ask better questions. When faced with problems, ask: "What approaches have you considered? What are the trade-offs?"
Establish team-owned standards. When engineers collectively define "good," they take ownership of maintaining quality themselves.
Celebrate learning. Publicly acknowledge both successful deliveries and valuable lessons from failures.
The Tangible Rewards
Building technical excellence through others transforms careers in concrete ways. Here are a few -
Reclaims your time. When teams handle technical challenges independently, you're no longer the bottleneck for every decision, freeing hours in your calendar.
Expands your scope. With a self-sufficient team, you can lead cross-functional initiatives that would otherwise be impossible with your limited bandwidth.
Creates promotion pathways. Senior leadership notices managers who scale their impact beyond a single team—a key criterion for advancement to director-level positions.
Improves team retention. Engineers stay longer under leaders who develop their capabilities rather than just directing their work, with data showing significantly lower turnover.
Increases strategic influence. When you're not buried in tactical code reviews, you can engage with product strategy and business decisions at a higher level.
This approach isn't just philosophically satisfying—it's career rocket fuel. Your value multiplies when you scale your technical judgment through others.
Your Leadership Journey
This week, I invite engineering managers reading this to try something uncomfortable, when a team member brings you a technical problem, don't offer a solution. Instead, ask guiding questions that help them discover their own path forward. Notice how they respond, how you feel, and what happens to the quality of their work.
Share your experiences. I would love to hear how this challenge goes for you.
📌 Hi, I'm Meena! 👋
I work with new Engineering Managers in Tech, to help them navigate the transition from coding to leading so that they thrive in their new role.
Recognise yourself here? Or perhaps you're seeing this play out with someone you manage? Get in touch and let's talk about how personalised support can make the difference.