How to Manage People Who Are Smarter (or More Skilled) Than You

March 28, 2026

adviceleadershipsenior-reportsimposter-syndrome

Here’s the secret nobody tells you when you get promoted: you’re probably going to manage people who are better than you at their actual job. And that’s not a bug — it’s the whole point.

If you were the smartest person on your team, your team would be in trouble. Your job isn’t to be the best engineer, designer, or analyst in the room. Your job is to make the best engineer, designer, or analyst in the room even more effective.

But knowing that intellectually and feeling it when a senior IC questions your decision in front of the whole team? Two very different things.

Here’s how to lead people who are more skilled than you without faking it, micromanaging, or hiding behind your title.

Why This Feels So Threatening

Let’s name it: imposter syndrome hits hardest when the gap between your title and your technical depth is visible to everyone.

You used to earn respect by being good at your craft. Now you’re in a role where your old currency — technical skill — is no longer the primary measure. But nobody gave you the new currency yet. You have to earn it, and that takes time.

As Harvard Business School notes, the transition from individual contributor to manager requires a fundamental identity shift — from “I deliver great work” to “I enable great work.” That shift is hardest when your reports are visibly exceptional at the thing you used to do.

The fear is simple: If they’re better than me at the work, why would they listen to me?

The answer is simpler: because you provide something they can’t provide for themselves.

What You Actually Bring to the Table

Stop trying to compete on their turf. You add value in ways that highly skilled ICs typically can’t or won’t do for themselves:

Context and priority. You know what leadership cares about, which projects are at risk, and where the political landmines are. Your senior engineer may write beautiful code, but they probably don’t know that the VP is about to cut the project’s budget.

Air cover. You shield them from unnecessary meetings, bureaucratic overhead, and distractions so they can focus on what they’re best at. This is unglamorous and wildly valuable.

Career advocacy. You fight for their promotions, compensation, and visibility. A brilliant IC who’s invisible to leadership is an IC who’ll leave.

Cross-team coordination. They see their own work deeply. You see how it connects to everything else. You’re the one making sure their brilliant solution actually integrates with what the other three teams are building.

Conflict resolution. When two smart people disagree, they need someone who can make a call and take the heat. That’s you.

The Behaviors That Build Credibility

1. Lead With Questions, Not Answers

When your senior report presents a technical decision, your first instinct might be to nod along and pretend you fully understand, or worse, to challenge it to prove you’re not clueless.

Instead, ask genuinely curious questions:

“What alternatives did you consider?”
“What’s the biggest risk with this approach?”
“If this fails, what does the fallback look like?”
“How does this affect the team’s other commitments?”

Good questions show strategic thinking without pretending to be the domain expert. And sometimes, the right question reveals a blind spot even the expert missed.

2. Be Transparent About What You Don’t Know

“I don’t have the technical depth on this — I trust your judgment on the implementation. But I want to make sure we’re aligned on the timeline and the dependencies.”

That sentence accomplishes three things: it shows humility, it respects their expertise, and it pivots to where you do add value.

Contrast that with a manager who pretends to understand, nods along, and then sends a contradictory email later. Skilled people spot fake understanding instantly, and it destroys trust.

3. Know When to Decide and When to Defer

This is the hardest calibration for new managers. A simple rule:

Defer on how (implementation details, technical approach, tool choices)
Decide on what and when (priorities, deadlines, scope, trade-offs)

“You know better than I do how to architect this service. I need your help figuring out whether we can ship it by Q3 given everything else on the roadmap.”

4. Give Them Ownership, Not Tasks

High-skill people don’t want to be told what to do. They want to be told what problem needs solving and then trusted to figure it out.

Bad: “Refactor the authentication module using this design pattern by Friday.”

Good: “Our auth flow is causing 30% of our support tickets. Can you own finding and implementing a fix? Let me know what you need from me.”

The second version treats them as the expert they are. It also makes them accountable for the outcome, not just the execution.

5. Fight for Them Loudly

Nothing earns loyalty from a senior IC faster than a manager who goes to bat for them. Publicly credit their work. Push for their promotion. Block scope creep on their projects. Make sure leadership knows their name.

If your best person feels invisible or undervalued, they’ll leave — and they’ll have offers within a week.

Common Mistakes to Avoid

Micromanaging to feel useful. When you can’t contribute technically, the temptation is to control the process instead. Resist it. Over-managing a senior IC is the fastest way to lose them.

Avoiding hard conversations because they’re “senior.” Being skilled doesn’t mean someone is above feedback. A senior IC who’s dismissive in code reviews or terrible at communicating with other teams still needs to hear it — from you.

Competing instead of amplifying. If you find yourself subtly undermining your report’s ideas to assert dominance, stop. This isn’t a competition. Their success is your success. Literally — that’s how management works.

Hiring people less skilled than you to feel safe. Some insecure managers do this, consciously or not. It’s organizational poison. Always hire the best person available, even if — especially if — they’re better than you.

The Paradox That Sets You Free

Here’s the thing about managing people smarter than you: the moment you stop trying to be the smartest person in the room, you become more effective as a manager.

Your value isn’t your individual contribution anymore. Your value is the multiplier effect — how much more productive, creative, and fulfilled your team is because you’re there.

A great manager of experts is like a great film director. The actors do the performing. The cinematographer handles the camera. The editor shapes the story. The director? They hold the vision, make the hard calls, and create the conditions for everyone else to do their best work.

You don’t need to be a better actor than your lead. You need to help them give the performance of their career.

That’s the job. And if you do it well, the smartest people you manage won’t just tolerate you — they’ll want to keep working for you.