Managing people who have been doing this longer than you

You won't win the experience argument. Don't try. Someone on your team has been doing this work since before you finished school, and any attempt to act like that isn't true will cost you the room in about a week.

What you can win is the competence argument. Not "I know more than you" — you don't. "I make good calls, I make them fast, and I follow through." That's a different claim, it's one you can actually back up, and older reports judge it quicker than anyone. They've worked for six managers. They can read you by the end of the first month.

So spend that month deliberately.

Start by asking, not telling

Your first one-on-one with a longer-tenured report shouldn't be about your plan. It should be about their work.

Four questions, and then you mostly listen:

• What's the part of your job you'd protect if I started changing things?
• What's broken that nobody's fixed, and why hasn't it been fixed?
• What do you want to be doing in two years?
• What did the last manager do that you'd rather I didn't?

That last one gets awkward answers, which is the point. Write them down in front of the person. Then actually change one of the things within a fortnight, and say so out loud: "You told me the Friday report was pointless. I killed it."

That single act does more for your standing than three months of good behavior. It says you listen, you have the authority to act, and you use it on their behalf. Experienced people have heard a lot of listening that went nowhere.

Don't overcorrect in either direction

New managers with older reports fail in two opposite ways.

The first is deference. You soften every instruction into a suggestion. You stop giving feedback because it feels presumptuous. You let a senior person quietly opt out of the process everyone else follows. Six months later you've got a two-tier team and the younger half has noticed, and they're right to resent it.

The second is chest-puffing. You over-explain decisions to prove you understand them. You restructure something in week two to plant a flag. You use "I've decided" as a verbal tic. This reads as insecurity, because it's.

The way through both is plainness. Say what you want, say why, say when. "I need the client review moved to Tuesdays because the exec meeting shifted. Any reason that doesn't work?" No apology, no posturing. Just the thing and the reason.

Be explicit about who decides what

Ambiguity is where age gaps turn into conflict. A twenty-two-year-old report assumes you decide. A fifty-five-year-old report with deep domain knowledge might reasonably assume they do. Neither of you says this out loud, and then one day you both act on your assumption at the same time in front of a client.

Head it off. Sit down and split the territory in writing:

• Their call, no check-in. Technical approach, sequencing, how they run their own work, calls inside their specialty.
• Their call, tell me after. Anything that touches another team, spend under a threshold you name, customer commitments inside existing scope.
• My call. Headcount, priorities across the team, anything with legal or money exposure, anything that changes what we promised someone else.

Then defend it. When you hand someone real decision rights, the next test is whether you take them back the first time you're nervous. Don't. Let them make a call you'd have made differently, watch it work out fine, and say nothing. That's the whole trust-building exercise in one move.

When you have to correct someone senior

It'll happen. Twenty years of experience doesn't stop anyone missing a deadline or being short with a colleague.

Handle it the same way you'd handle it with anybody, with one adjustment: lead with the behavior and the impact, and skip the teaching. Don't explain why deadlines matter to someone who has met ten thousand of them. That's the condescension they're braced for.

"The spec was due Thursday and it landed Monday. Procurement lost their slot and it pushed the whole build a week. What happened?"

Then stop talking. Let the silence sit. Experienced people usually give you a straight answer if you've given them a straight question, and often the answer is something you needed to know — a dependency you didn't see, a request from above you weren't copied on.

What kills you is saving it up. If you let three of these slide because the conversation felt uncomfortable, the fourth one comes out as a speech about attitude, and now you're the manager who ambushed someone over a year of grievances.

The person who wanted your job

If one of your reports applied for the role you got, you need to name it. Not in week one — let the dust settle a fortnight — but you do need to name it.

"I know you went for this. I imagine that stings. I'd like to work out how you get to the next thing, and I'd rather do that with you than have it sit between us."

Some people will take that offer and become your strongest ally. Some will be polite and start looking. Both are better than pretending. What you can't do is make a promise you don't control — don't say "you'll have my job in two years" unless you genuinely have the power to make that happen. Say what you'll actually do: put their name forward, give them the visible project, tell your boss they're ready.

Careers don't stop, and neither do theirs

Assuming a fifty-eight-year-old is coasting is both insulting and usually wrong. Plenty of people want new scope late in a career. Some want to move sideways into mentoring or a specialist track. Some genuinely do want stability and predictable hours, and that's a legitimate thing to want, not a character flaw.

You find out by asking, once a quarter, the same way you'd ask a graduate. The question that works: "In twelve months, what would make you glad you stayed?"

And be careful with the small stuff. Jokes about anyone being bad with technology, remarks about "old school" methods, a tone that treats long tenure as inertia — those land harder than you think and people don't tell you they landed. Same goes the other way, by the way. If someone on your team refers to you as "the kid" in front of clients, deal with it privately and once.

Use what they've got

The best thing about managing someone with more mileage than you is that they've seen this movie. Ask directly: "We're about to do a big reorg. You've been through three. What goes wrong?"

You'll get answers no strategy deck contains. Which department quietly blocks things. Which promise the company made in 2014 that people still remember. Why the last attempt at this failed and who got blamed.

Make a habit of it. Take the advice visibly when it's good, and when you go the other way, tell them why. "I heard you on the phased approach. I'm going faster because the funding window closes in March. If it goes sideways, you get to say you told me."

They will, too. And the fact that you left the door open for it's exactly why they'll back you when it counts.