
A new manager may know the organization’s current priorities, but a team member may know the work, customers, systems, or industry far better. That difference can create uncertainty on both sides. You may worry about appearing uninformed, while the experienced employee may wonder whether your decisions are credible or useful. The answer is not to compete with their knowledge or pretend to have all the answers. Effective management begins by respecting expertise, clarifying authority, and creating a working relationship in which experience supports good decisions rather than quietly undermining them.
How to Manage Someone With More Experience Than You Effectively
#1. Acknowledge Their Experience Without Surrendering Your Role
Start by recognizing what the employee brings to the team. Specific acknowledgment is more credible than vague praise. You might note their years serving important clients, their knowledge of a complex process, or their history with a recurring operational problem. This shows that you have paid attention and are not trying to erase the value of their experience.
At the same time, respect does not mean handing over your management responsibilities. Your role may include setting priorities, allocating work, making decisions, giving feedback, and representing the team’s needs. The employee’s expertise should inform those responsibilities, not automatically replace them.
You have a deeper understanding of this process than I do, and I want to make good use of that knowledge. I’m still responsible for setting the team’s priorities and making final decisions, so I’d like us to be clear about how your expertise can shape those decisions.
This balance prevents two common errors: acting as though experience is irrelevant or becoming so deferential that you stop managing.
#2. Learn Before You Change Things
New managers often feel pressure to demonstrate authority quickly. That can lead to unnecessary changes before they understand why current practices exist. Spend time observing the work, reviewing relevant information, and asking experienced employees to explain the reasoning behind established procedures.
Learning does not require endless delay. Set a reasonable period for gathering information, then begin making decisions based on what you have learned. Ask questions that reveal both the visible process and the hidden constraints, such as customer expectations, technical dependencies, staffing realities, or previous attempts to solve the problem.
Useful questions include:
- What part of this process works well?
- Where does it usually break down?
- What has already been tried?
- Which risks should I understand before changing it?
- If you were responsible for improving this, what would you examine first?
You do not need to adopt every recommendation. The purpose of listening is to improve the quality of your judgment, not to avoid making one.
#3. Clarify Decision Rights And Expectations
Experience-related tension often comes from uncertainty about who decides what. An employee may assume that long service gives them informal authority, while a new manager may assume that formal authority will be accepted without discussion. Neither assumption is reliable.
Clarify the areas in which the employee has autonomy, the decisions that require consultation, and the matters you must decide yourself. Put important expectations in writing after a meeting, especially when responsibilities overlap. This is not about creating bureaucracy; it is about reducing avoidable conflict.
For example, you might establish that the employee owns day-to-day technical recommendations, while you set deadlines, approve changes that affect other departments, and handle performance or staffing decisions. If the employee disagrees with a decision, they should be able to raise the concern directly, but they should also understand how the final decision will be made.
Clear boundaries make collaboration safer. They also prevent experience from becoming an unofficial chain of command that confuses other team members.
#4. Ask For Advice Without Making Every Decision A Referendum
Experienced employees can provide valuable insight, but consultation does not mean that every decision must receive their approval. If you ask for advice and then treat disagreement as a veto, you may unintentionally transfer your authority to the employee. If you never ask for advice, you waste knowledge that could improve the outcome.
Frame requests for input around a specific decision and a specific deadline. Explain what you are trying to decide, what constraints apply, and what kind of information would be useful. Then evaluate the advice alongside budget, strategy, policy, customer needs, and input from others who are affected.
I’d like your view on the implementation risks before I finalize the plan. Please focus on what could cause delays or quality problems. I’ll consider that with the timeline and resources we have, then I’ll confirm the decision by Friday.
If you choose a different course, explain enough of your reasoning to preserve trust. You do not need to defend every detail, but unexplained reversals can make consultation feel performative.
#5. Establish Mutual Feedback
A productive relationship should allow feedback in both directions. You can invite the experienced employee to identify gaps in your understanding, while making clear that feedback should address observable actions and their effects rather than your age, background, or perceived legitimacy.
Be equally willing to give feedback when the employee’s conduct affects the team. Experience does not excuse interrupting colleagues, resisting every change, withholding information, bypassing you, or presenting personal preferences as mandatory requirements. Address the behavior promptly before frustration turns into a broader judgment about the person.
A useful conversation might sound like this:
I value your knowledge, and I want you to challenge decisions when you see a genuine risk. In today’s meeting, you dismissed the proposed approach before others had finished explaining it. That made it harder for the group to consider alternatives. In future discussions, please raise the concern after the explanation and distinguish a confirmed risk from a preference.
Feedback should be specific, proportionate, and connected to expectations. The same standard should apply to every team member, including you.
#6. Give Them Meaningful Ownership
An experienced employee may become frustrated if management reduces their role to following instructions from someone newer to the work. Give them meaningful ownership where their knowledge can produce value. This might involve leading a process review, mentoring a colleague, managing a customer relationship, documenting technical knowledge, or testing an improvement.
Ownership should come with a clear purpose, authority, and measure of success. Do not assign a vague project merely to keep the employee occupied, and do not use delegation as a way to avoid decisions that belong to you. Define the outcome, resources, boundaries, and point at which you will review progress.
This approach benefits the whole team when it is handled carefully. It recognizes expertise without creating a privileged position. Make sure responsibilities and opportunities are distributed fairly, and avoid allowing one experienced employee to become the only person who knows how critical work gets done.
#7. Address Undermining Behavior Directly And Fairly
Disagreement is not the same as insubordination or undermining. An experienced employee may reasonably question a plan, identify a serious risk, or propose a better method. The concern arises when they repeatedly ignore decisions, give conflicting instructions, discredit you in front of colleagues, or encourage others to disregard agreed expectations.
Before confronting the issue, document specific incidents, including what happened, who was affected, and what expectation was unclear or breached. Then speak privately and allow the employee to explain. You may discover a misunderstanding, a legitimate operational concern, or a recurring conduct problem. Respond to the actual issue rather than assuming hostile motives.
I want to address a pattern I’ve noticed. After we agreed on the revised schedule, you told two colleagues to follow the old process without bringing the concern back to me. If you believe the decision creates a problem, I expect you to raise it directly. Once a decision is made, I also expect you to support the agreed process unless there is a new and serious risk.
If the behavior continues, follow established performance-management or HR procedures. Respect for experience should never require tolerating conduct that damages clarity, fairness, or team performance.
When Experience Creates Tension Between Manager And Employee
Tension does not always mean that either person is acting badly. A long-serving employee may have seen several managers arrive with ambitious plans and leave after a short time. They may therefore be cautious about new initiatives. A new manager may interpret that caution as resistance, while the employee may see the manager’s urgency as a failure to understand operational reality.
Separate the content of the disagreement from the manner in which it is expressed. Ask whether the employee is identifying a real constraint, protecting an established preference, or reacting to a change in status. You do not need to speculate about motives. Focus on what can be observed and tested.
A useful response is to convert disagreement into evidence. Ask what outcome the employee expects, what risk they see, and how the concern could be evaluated. Where practical, use a limited trial, defined review date, or measurable criterion instead of arguing indefinitely. This allows the manager to remain accountable while giving experience a proper role in improving the decision.
If the relationship remains difficult, involve an appropriate internal resource such as your own manager or HR, particularly when communication has broken down or conduct is affecting the wider team. Seek help with the working problem, not with a character judgment about the employee.
A Practical Conversation For Starting The Relationship
An early conversation can establish the tone for the relationship before frustration accumulates. Keep it direct and collaborative. Explain that you respect the employee’s experience, clarify your responsibilities, and invite honest information about the work. Avoid promising that you will accept every recommendation or suggesting that your role is merely administrative.
You can adapt the following wording to your circumstances:
I’m looking forward to working with you. I know you have substantial experience with this team and the work we deliver, and I want to understand what you think is important for me to learn early on.
I also want to be clear about how I’ll work. I’ll ask for your input on decisions where your knowledge is especially relevant, and I’ll explain priorities and expectations clearly. I’m responsible for the team’s overall direction and decisions, but I don’t expect to make those decisions without listening to the people closest to the work.
If you disagree with something I decide, please raise it directly. I’ll do the same if I see a behavior or performance issue that needs attention. My aim is for us to be candid, respectful, and focused on producing good work.
After the conversation, follow through. Credibility grows less from one impressive meeting than from consistent decisions, fair treatment, and willingness to correct your own mistakes.
Closing Thoughts
Managing someone with more experience than you requires neither defensiveness nor excessive deference. Respect their knowledge, learn before changing important practices, and use their advice without surrendering your responsibility to decide. At the same time, hold every team member—including experienced employees—to clear standards for cooperation and conduct. Your next step should be a straightforward conversation about what you need to learn, what you are accountable for, and how you will handle disagreement. That clarity creates the foundation for trust and effective work.
