Leadership
Stay Technical or Lose the Room
Oct 3, 2025
Last quarter, I sat in on a design review for our fraud detection service. Ten minutes in, I realized we were solving the wrong problem—not because I’m smarter than my team, but because I’d traced production logs the week before and saw what was actually breaking. That intervention saved three weeks of wasted effort and prevented a pattern that would’ve generated a mountain of costly false positives.
Moments like this highlight a tension every engineering leader faces: how do you stay technically credible without becoming a bottleneck?
I’ve failed on both sides—early by staying too deeply entrenched in code and missing strategic opportunities, and later by drifting too far into meetings and losing my team’s respect. A senior engineer once asked if I’d actually reviewed the architecture before approving a refactor. He was right to ask.
This is the credibility tax—the permanent cost of leadership. You can’t avoid paying it. You can only choose whether to pay it deliberately, in small installments, or let it compound into a crisis when your team stops listening.
The Cost of Losing Technical Credibility
Engineers can sense when a manager has lost touch. It’s not about writing every line of code—it’s about asking the right questions, recognizing trade-offs (like consistency vs. availability in a distributed system), and knowing when a problem is systemic versus symptomatic.
Without technical credibility, leaders struggle to:
Influence architecture decisions
Align timelines with technical reality
Shield their teams from unrealistic demands
Know when something takes two days vs. two weeks
A 2022 Stack Overflow survey found that 68% of developers cited “technically incompetent leadership” as a notable reason for considering leaving their jobs.
As Michael Lopp puts it: “Your credibility is your currency.” And in engineering leadership, technical depth is how you earn it.
The paradox is that you can’t scale by being the senior engineer on every project. If you try, you’ll throttle your team’s growth and burn yourself out.
Common Anti-Patterns
I’ve seen (and been) each of these:
The Absentee Architect. Drifts into pure people management. The team bypasses them on technical calls.
The Hero Engineer. Can’t let go of IC work. Becomes the bottleneck. Direct reports stagnate.
The Meeting Collector. Shows up everywhere but adds nothing substantive. Real conversations happen without them.
All three stem from the same root cause: failing to choose where to invest technical energy and where to trust your team.
What Leadership Actually Requires
Technical depth keeps you credible—but it doesn’t make you a leader. Leadership requires system-level thinking applied to organizations:
Direction: Translate fuzzy product goals into clear technical choices. When a PM says “we need to move faster,” you decide whether that means parallelizing API calls, cutting scope, or pushing back entirely.
Support: Remove real obstacles—broken API contracts, blocked access, or missing production analytics.
Impact: Connect engineering work to business outcomes. “We refactored authentication.” → “We reduced account takeover risk by 40%.”
These responsibilities put you in rooms where no code is written—but they still demand technical fluency.
How to Stay Technical Without Becoming a Bottleneck
The best leaders I know are deliberate about their credibility tax. They pick their battles, avoid being on every critical path, and signal depth without competing with their staff engineers.
Pick a Technical Anchor
Choose one or two areas to stay sharp. I focus on mobile engineering and observability—monitoring patterns, tracing distributed requests, and reading production metrics. I let myself get rusty on backend frameworks and infrastructure tooling, and lean on staff engineers for depth in those areas.
Do System Walkthroughs
Instead of nitpicking code reviews, trace a request end-to-end through logs, shadow QA sessions, or watch error rates during deploys. Last month, I caught a rollback gap just by monitoring dashboards for an hour. That’s credibility without being on the keyboard.
Master the Catalytic Question
High-leverage leaders ask better questions:
“What’s the riskiest assumption we’re making?”
“If this failed at 3 am, what’s hardest to debug?”
“What decision are we deferring that will cost more later?”
“Where is Conway’s Law biting us right now?”
Questions like these force honest conversations and show that you’re paying attention.
Elevate Experts, Don’t Compete
When my staff engineer pushes back on architecture, I don't defend my ego. Last month, she challenged my caching approach—and she was right about the memory implications. I said so in front of the team. That builds her credibility—and mine.
Audit Your Calendar
I track the ratio of strategy vs. technical time. If it drifts beyond roughly 85/15, I’m in danger of losing touch. That 15% is sacred. Protect it.
The Credibility Tax Never Goes Away
Here’s the truth: you never “solve” this tension. The best leaders don’t escape it—they accept it. They build systems that let them stay technical without blocking progress. They maintain enough depth to make hard calls while creating space for their teams to grow.
The alternatives fail both ways: pure managers lose trust, over-technical managers lose scale. The credibility tax is permanent. But paying it deliberately is what separates leaders who scale from those who stall.
What’s your anchor? Where have you seen leaders lose credibility—or maintain it against the odds?
Worth reading:
