Managing Employees More Experienced Than You: Lead Without Pretending

You have the manager title. Someone on your team has deeper technical knowledge, longer organisational history or experience doing your role. That does not require you to win an expertise contest. It requires a clear agreement about the outcome, their contribution and your management responsibilities.

 

Start by learning what they know, clarifying decision rights and removing a real obstacle. Credibility can come from useful follow-through rather than pretending you already know every answer.

 

Experience and authority are different questions

 

Illustrative scenario — not a customer testimonial. A newly promoted manager asks an experienced colleague to prepare a customer recommendation. The colleague points out that an earlier version failed because of a technical constraint. The manager hears a challenge to their authority and dismisses the objection. The team loses useful information, while the original constraint remains.

 

A better response is: “Show me the constraint and the options it rules out. We still need a recommendation by Friday. Let's use the evidence to choose a workable approach.” This acknowledges expertise without giving up responsibility for the decision process.

 

Experience is also not the same as age. Do not assume an older colleague resists change, or that a younger colleague lacks relevant knowledge. CCL's guidance on multigenerational teams cautions against age-based assumptions and encourages understanding individuals. Read the CCL guidance.

 

1. Learn the context before redesigning the work

 

Book a focused conversation, not an open-ended request to “teach me everything.” Bring a current outcome or recurring problem.

 

Ask:

 

• What constraint is easy for a newcomer to miss?

• Which part of this process protects quality or safety?

• What has already been tried, and what evidence do we have?

• Which decision would reduce the most avoidable delay?

• Where does the team depend too heavily on one person's knowledge?

Take notes on the work, not personality labels. Verify material claims with the appropriate records and people; long tenure is useful context, not automatic proof that every conclusion is correct.

 

2. Say what you own and what they own

 

Vague ownership creates two common problems: the manager micromanages expert work, or the expert becomes the unofficial manager for every difficult choice.

 

Adapt this original script: “You own the technical recommendation and the evidence behind it. I own aligning the priority, confirming resources and ensuring the decision reaches the right approver. Let's name anything outside either of our authority before we begin.”

 

For a small project, write:

 

• Outcome: the result needed, with a clear completion check.

• Expert contribution: the analysis, recommendation or implementation the employee owns.

• Manager contribution: priority, coordination, resources and appropriate escalation.

• Decision: who decides, who must be consulted and by when.

• Review: the agreed checkpoint, not continuous unannounced checking.

Confirm this arrangement with your own manager where necessary. A template cannot create authority that the organisation has not granted.

 

3. Delegate a result, not a demonstration of obedience

 

“Keep me copied on everything” is not a substitute for a useful review plan. Choose checkpoints based on risk, dependencies and unfamiliar parts of the work.

 

Example: “Please recommend one approach by Thursday. Compare customer impact, delivery risk and cost. You choose how to develop the analysis. Let's review the two highest-risk assumptions on Tuesday before you complete it.”

 

Explain any non-negotiable quality or safety constraints. If the employee proposes a different method, assess it against the outcome and those constraints. Do not reject it just because it is not your preferred method.

 

Prepare before your next conversation

 

Send me the free first-week checklist

 

Enter your email on the next page to receive the checklist. Optional marketing updates are separate from receiving the requested file.

 

4. Distinguish disagreement from a broken agreement

 

An employee questioning an assumption can improve a decision. An employee repeatedly bypassing an agreed approval or deadline is a different issue. Describe the specific event rather than labelling the person “resistant.”

 

When they challenge the plan: “Which assumption concerns you? What evidence or alternative should we consider before deciding?”

 

When they bypass an agreed route: “We agreed the recommendation would go through [route] before release. It was sent before that review. What happened, and what needs to change for the next release?”

 

When the evidence is incomplete: “I do not know enough to resolve this yet. We will check [source/person] and return to the decision by [date].”

 

Do not turn constructive disagreement into a loyalty test. For continuing or formal performance concerns, use the organisation's procedures and appropriate support.

 

5. Ask about development instead of assuming they need nothing

 

An experienced colleague may want a different type of work, better access to decisions, a manageable workload or a chance to develop another skill. They may not want the management path you chose.

 

Try: “What would you like more opportunity to do, and what support would make that realistic?” Separate their preferences from promises you cannot make. If you offer a development opportunity, check team capacity and use legitimate criteria for comparable decisions.

 

Avoid making them the permanent trainer simply because they know the most. Agree the time, scope and recognition of knowledge-sharing work rather than quietly adding it to an already full role.

 

A useful agreement you can finish today

 

Choose one current task and complete this original working note:

 

“By [date], we need [outcome]. [Employee/role] will own [contribution]. I will remove or escalate [blocker]. We will consult [role] about [constraint]. [Decision-maker] decides by [date]. We will review [specific evidence] at [checkpoint].”

 

Read it together. Ask which part is unclear. The output is an agreed route through the work, not a statement that one person is more important.

 

Questions you may be asking

 

Should I admit that I know less about the technical work?

 

Be specific about what you need to learn. “I need to understand this risk before approving the plan” is useful. Constantly apologising for being the manager is not. Learn, check the evidence and fulfil your own responsibilities.

 

What if the experienced employee used to be my manager?

 

Do not assume the old arrangement still applies. Acknowledge the changed reporting relationship and agree responsibilities for current work. Ask your manager for help where there is ambiguity or a conflict of interest.

 

How can I earn credibility quickly?

 

Choose a small commitment within your authority and complete it: clarify a priority, resolve access, obtain a decision or give a dated update. Do not promise respect, friendship or a particular career outcome in exchange.

 

Turn clearer responsibilities into a repeatable plan

 

Essentials — US$9: first-week guide, printable and editable workbook, manager-alignment and team-meeting planners, first 1:1 listening worksheet, boundaries and fairness tools, and checklist.

 

I want my first-week tools — US$9

 

Complete — US$29: everything in Essentials plus the Days 8–30 guide and workbook, delegation and decision-boundary tools, workload trade-off planning, weekly follow-up tracker and Day 30 review agenda.

 

I want the complete 30-day toolkit — US$29

 

Eligible Essentials buyers receive US$9 credit and pay US$20 more before applicable tax when upgrading under the original purchase account. Confirm the credit at checkout. Complete already includes Essentials; existing Complete buyers do not need to purchase it again.

 

Compare the tools · Read the broader former-peer transition guide

 

Sources and editorial boundaries

 

Knowledge Skill Bank editorial team · 27 September 2026. Source checked: Center for Creative Leadership, *How to Lead a Multigenerational Workforce or Team*. This source supports the caution against age stereotypes; it does not establish that our scripts or products produce a particular result. CCL has not endorsed Knowledge Skill Bank. The scenario, scripts and working note are original educational tools, not testimonials. This is general workplace education, not HR, employment-law, medical or disciplinary advice.