A manager sits quietly in a code review, a design critique, or a technical planning session, genuinely aware that the person they’re managing has deeper, more current expertise in the actual work than they do themselves. This is a genuinely common situation, particularly as careers progress and management responsibilities expand beyond any single person’s ability to remain the most technically capable person in every room they lead — and it’s a situation many managers navigate with real, unspoken discomfort, uncertain how to lead credibly someone whose actual skill in the work itself has surpassed their own.
Why This Situation Is More Common Than It’s Often Acknowledged to Be
As careers progress into broader management responsibility, it becomes structurally inevitable that a manager will, at some point, lead people whose specific technical skill in a narrower domain exceeds their own — nobody can remain the most technically capable person in every specialised area a growing team eventually covers. This is a normal, expected feature of career progression into management, not a personal failing or a sign that someone has been promoted beyond their genuine competence, even though it can feel that way in the moment, particularly for someone who built their early career on being the most technically skilled person in the room.
Why Discomfort With This Situation Often Comes From a Misunderstanding of the Manager’s Actual Role
Much of the discomfort in this situation traces back to an unconscious, mistaken assumption: that a manager’s legitimacy depends on being the most technically capable person on their team. In practice, the genuine value a manager provides is usually different in kind from technical execution itself — removing obstacles, providing context and prioritisation, developing people, making decisions that require a broader view than any individual contributor’s specific technical lens provides. Recognising this distinction directly helps dissolve much of the discomfort, since it reframes the actual question from “am I more skilled than this person” to “am I providing genuine value of a different, complementary kind.”
What Actually Undermines Credibility in This Situation
Pretending to have technical expertise you don’t genuinely have. Attempting to fake deep technical knowledge in front of someone who genuinely has it is usually transparent, and tends to damage credibility considerably more than honest acknowledgement of the genuine skill gap ever would.
Making technical decisions unilaterally without genuinely consulting the person with deeper expertise. Overriding a more technically skilled team member’s judgement on a matter genuinely within their specific expertise, without a good, transparent reason, tends to produce resentment and, often, a worse actual decision than deferring to genuine expertise would have.
Being unable to add any value at all beyond the technical work itself. A manager who has nothing genuine to offer beyond what the more skilled team member could already provide themselves — no context, no prioritisation, no advocacy, no development support — genuinely raises a legitimate question about what the management layer is actually contributing.
What Genuinely Builds Credibility Instead
Openly acknowledging the specific skill gap, without excessive self-deprecation. A direct, matter-of-fact acknowledgement — “you know this specific area considerably better than I do, and I want your genuine judgement on it” — tends to build more credibility than either pretending otherwise or over-apologising for a genuinely normal situation.
Providing genuine value in the areas where a manager’s broader view actually matters. Context about organisational priorities, advocacy for resources, protection from unnecessary distraction, genuine investment in a person’s development — these are real contributions a manager can make regardless of the specific technical skill gap, and leaning into them deliberately builds credibility on a foundation that doesn’t depend on technical parity.
Asking genuinely good questions, even without deep technical expertise. A manager doesn’t need equivalent technical knowledge to ask sharp, clarifying questions that genuinely help surface important considerations — “what happens if this assumption turns out to be wrong” is a valuable question regardless of whether the person asking it could have built the technical solution themselves.
Trusting genuine expertise on matters genuinely within its domain. Deferring visibly and consistently to a more skilled team member’s judgement on matters genuinely within their specific expertise, rather than second-guessing it reflexively, signals a secure, healthy relationship with the actual limits of the manager’s own technical knowledge.
Why This Requires Genuine, Not Performed, Humility
There’s a meaningful difference between genuine humility about a real skill gap and performed humility that’s actually a subtle form of self-protection or fishing for reassurance. Genuine humility involves actually deferring to expertise where it’s warranted, actually asking honest questions rather than rhetorical ones, and actually valuing the more skilled person’s contribution rather than feeling threatened by it — team members tend to sense the difference between genuine and performed humility fairly reliably, and only the genuine version actually builds the kind of trust this situation depends on.
Handling the Specific Discomfort of Giving Feedback in This Context
Feedback on genuinely technical matters, delivered by a manager without equivalent technical depth, deserves particular care — it’s often more appropriate and more credible to focus feedback on process, collaboration, communication, and how work fits into broader priorities, than to attempt technical feedback in an area where the manager genuinely lacks the depth to evaluate it well. This doesn’t mean avoiding technical topics entirely, but it does mean being honest about which kind of feedback the manager is genuinely positioned to offer credibly, and which kind should come from elsewhere — a technical lead, a peer reviewer, a more senior specialist — rather than the manager stretching into territory where their own judgement is genuinely less reliable.
A Practical Scenario
A newly promoted engineering manager finds herself leading a senior engineer with considerably deeper, more current technical expertise in a specific area than she has herself, and initially feels a real, persistent discomfort about how to lead credibly given this gap. Rather than attempting to mask the gap or avoid technical discussions altogether, she addresses it directly and matter-of-factly in an early one-on-one — acknowledging his deeper expertise honestly, and explaining clearly what she does see as her own genuine contribution: securing the resources and organisational context he needs, protecting his focus from unnecessary distraction, and genuinely advocating for his growth and visibility within the broader organisation.
Over the following months, she consistently defers to his technical judgement on matters genuinely within his expertise, while providing real, valued input on prioritisation, cross-team coordination, and career development that he genuinely couldn’t have provided for himself in the same way. The relationship develops into one of genuine mutual respect, with him explicitly noting in a later conversation that her honesty about the skill gap, paired with the real value she consistently provided elsewhere, built more trust than a manager who’d tried to project technical authority she didn’t actually have ever could have.
Common Mistakes
Attempting to fake technical expertise you don’t genuinely have. This is usually transparent to someone with genuine depth in the area, and damages credibility considerably more than honest acknowledgement of the skill gap would.
Overriding a more skilled team member’s technical judgement without good reason. This tends to produce both resentment and, often, a worse actual decision than deferring to genuine expertise on matters genuinely within its domain.
Providing no genuine value beyond the technical work itself. A manager needs a real, distinct contribution — context, advocacy, development support, prioritisation — that doesn’t depend on technical parity with the people they’re leading.
Confusing genuine humility with performed, self-protective humility. Team members tend to sense the difference, and only genuine deference and genuine curiosity actually build the trust this specific situation depends on.
Action Steps
- If you’re managing someone with deeper technical expertise than your own, acknowledge the specific gap directly and matter-of-factly, rather than avoiding the topic.
- Identify explicitly what genuine value you provide beyond the technical work itself, and lean into those contributions deliberately.
- Practise asking genuinely good, clarifying questions in technical discussions, rather than either staying silent or attempting to fake deeper expertise.
- Notice the next time you’re tempted to override a more skilled team member’s judgement, and consider whether deferring to their genuine expertise would serve the outcome better.
- Direct technical feedback toward those better positioned to offer it credibly, focusing your own feedback on process, collaboration, and broader priorities instead.
Key Takeaways
- Managing someone with deeper technical skill than your own is a normal, structurally common feature of career progression into management, not a personal failing.
- Much of the discomfort traces back to a mistaken assumption that a manager’s legitimacy depends on technical parity, when the genuine value a manager provides is usually different in kind.
- Pretending to have expertise you don’t, overriding genuine expertise without reason, and providing no distinct value all undermine credibility in this situation.
- Openly acknowledging the skill gap, providing genuine value elsewhere, asking sharp questions, and deferring to real expertise all build credibility on a more sustainable foundation.
- Genuine humility, not performed humility, is what actually builds trust — team members tend to sense the difference fairly reliably.
Why This Skill Becomes More Valuable as Careers Progress
The ability to lead genuinely skilled people without technical parity becomes an increasingly central management skill the further a career progresses, since senior leadership roles almost inevitably involve overseeing specialists across a growing range of domains no single person could master personally. Building comfort with this dynamic early, rather than avoiding roles that require it, prepares a manager well for the reality that awaits at more senior levels of almost any organisation.
Recognising When You’ve Genuinely Earned Technical Trust
Over time, as a manager builds genuine, accumulated exposure to a domain even without becoming a specialist in it themselves, their own judgement calls within that domain often become more reliable, even while remaining genuinely less skilled than a true specialist. Recognising this gradual, real shift honestly — neither overestimating newly developed judgement nor underselling genuinely accumulated context — helps a manager calibrate appropriately as the working relationship and their own familiarity with the domain both continue to mature over time.
A Final Word on Genuine Confidence
Ultimately, navigating this situation well comes down to a genuine, secure sense of what a manager’s actual role is, independent of technical comparison — a security that, once genuinely internalised, makes the entire dynamic considerably less fraught than it initially feels to someone new to leading people more skilled than themselves in a specific domain.
Conclusion
Managing someone whose technical skill exceeds your own is a genuinely common, structurally normal part of career progression into management, and navigating it well requires recognising that a manager’s actual value lies in something different from technical parity — context, advocacy, prioritisation, genuine development support. Acknowledging the skill gap honestly, providing real value in the areas where it genuinely matters, and deferring to genuine expertise where it’s warranted all build considerably more credibility than either pretending the gap doesn’t exist or feeling threatened by a colleague’s genuine capability.
Frequently Asked Questions
Is it normal to manage someone more technically skilled than I am?
Yes, genuinely — this becomes structurally common as careers progress into broader management responsibility, since nobody can remain the most technically capable person in every area a growing team eventually covers.
Should I acknowledge the skill gap directly with the person I’m managing?
Generally yes — a direct, matter-of-fact acknowledgement tends to build more credibility than either pretending the gap doesn’t exist or over-apologising for a genuinely normal situation.
What should I actually contribute if I’m not the most technically skilled person on my team?
Context about organisational priorities, advocacy for resources, protection from unnecessary distraction, and genuine investment in development are all real, valuable contributions independent of technical parity.
Should I give technical feedback even without deep expertise in the specific area?
Generally, it’s more appropriate to focus your feedback on process, collaboration, and broader priorities, directing genuinely technical feedback toward those better positioned to offer it credibly.
How can I tell if my humility about this situation is genuine or just performative?
Genuine humility involves actually deferring to expertise where warranted and actually valuing the person’s contribution; performed humility tends to be a subtler form of self-protection, and team members usually sense the difference.
Does this situation ever resolve, or is the skill gap permanent?
It can shift over time as a manager builds broader context and judgement, though the underlying dynamic — a manager’s value being distinct from technical parity — remains true regardless of how the specific gap evolves.