Managing Someone Older or More Experienced Than You

Someone on your team has been doing this for twenty years. They were here before you, they've forgotten more about the domain than you currently know, and for reasons of timing or temperament they now report to you. In meetings they're civil. When you make a call they don't like, there's a pause before the 'sure' that everybody hears.

You've probably overcorrected in one of two directions: avoiding them entirely — no feedback, no direction, effectively an unmanaged employee — or asserting authority in ways that look exactly as insecure as they feel. Both cost you the room, because the rest of the team is watching how you handle this more closely than they're watching anything else you do.

Authority and expertise are different things, and new managers conflate them. Your role gives you decision rights, resource allocation, and accountability for outcomes. It does not give you superior technical judgment and was never supposed to. When you behave as though the title conferred expertise, an experienced person sees it immediately, and respect drains fast.

On their side, there's often a real grievance that isn't about you. They may have wanted this role, or wanted out of the ladder entirely and resent being managed by someone still climbing it, or have watched three managers come and go and concluded that outlasting is the strategy. Not knowing which of these you're dealing with is why the first conversation matters so much.

The third dynamic is unstated: many veterans are not looking for advancement, they're looking for relevance. A manager who treats their experience as an obstacle to route around creates an adversary. A manager who routes work through it gains the most useful ally on the team.

Not every difficult veteran is a misunderstood asset. Some are coasting on reputation, some are actively undermining you in rooms you are not in, and some stopped learning a decade ago and expect seniority to cover it. The test is not whether they challenge you — challenge is healthy — but whether the challenge happens in front of you or behind you, and whether it is ever followed by commitment once the decision is made.

When it is genuinely a performance or conduct problem, the fix is the same as it would be with anyone: specific examples, a clear standard, a date, and a written record. What changes with an experienced person is your own nerve, because the conversation feels more consequential. It is not. Handling it the same way you would with a junior member of the team is precisely what demonstrates that the standard belongs to the role and not to the person's age.

They bring you the objection before the decision rather than after it. A veteran who waits until afterward has decided that input is not worth the breath.

They start mentoring without being asked. Experienced people invest in the next generation when they feel relevant and withhold it when they feel managed around.

The pause before the yes disappears. Everybody in the room can hear that pause, including the people it is not about, which is why closing it changes how the whole team reads you.

Ask them, in front of the team, for their read on something hard — and then act on it when it's right, with attribution. It costs you nothing, it converts a status contest into a working relationship, and it demonstrates to everyone watching that your authority is secure enough to spend. Managers who can't do this end up with an experienced employee they're afraid of; managers who do it end up with the strongest advocate in the room.