When someone ignores your instructions, challenges your decisions, or behaves as though your role carries no weight, managing them can become unnecessarily difficult. The problem is not always simple insubordination. It may involve unclear responsibilities, a history of poor communication, legitimate disagreement, or behavior that undermines the team. The most effective response is neither passive tolerance nor an immediate power struggle. You need to clarify expectations, address observable conduct, listen carefully, and follow through consistently. The following approach will help you manage the situation without turning every interaction into a contest of authority.
How to Manage Someone Who Doesn’t Respect Your Authority Professionally
#1. Define What “Disrespect” Looks Like in Practice
Before confronting the person, separate the feeling of being disrespected from the specific conduct causing the problem. “They do not respect me” is a conclusion; “They repeatedly interrupt me, disregard agreed instructions, and criticize decisions in front of colleagues” describes observable behavior. This distinction matters because you can address conduct fairly, while assumptions about someone’s attitude or motives often create unnecessary conflict.
Write down two or three recent examples, including what happened, who was present, and how the behavior affected the work. Consider whether the issue is a single disagreement, a recurring pattern, or a genuine misunderstanding about your role. Also ask whether the person is challenging your authority or raising a legitimate concern in an uncomfortable way. Employees should be able to question decisions respectfully.
Focus on facts such as:
- Instructions being ignored without discussion.
- Decisions being reversed without authorization.
- Meetings being disrupted or dominated.
- Colleagues being encouraged to bypass you.
- Commitments being missed after expectations were clearly stated.
This preparation keeps the conversation specific and reduces the temptation to use labels such as “difficult,” “disloyal,” or “unprofessional.”
#2. Check Whether Your Authority and Expectations Are Clear
Sometimes a person appears resistant because responsibility has not been communicated clearly. If different managers give conflicting instructions, if your decision-making scope is uncertain, or if the person has historically worked independently, their behavior may reflect confusion rather than deliberate defiance. You should still address the impact, but clarity may solve the problem faster than a reprimand.
Review the practical boundaries of your role before raising the issue. What decisions can you make? Which matters require approval? What standards, deadlines, reporting lines, or procedures apply? If you are a new manager, explain how your working relationship will operate rather than expecting the person to infer it.
You might say:
I want to clarify how we will handle project decisions. I am responsible for setting the priorities and approving changes to the timeline. I welcome your recommendations, but please raise them with me before changing the plan or directing others.
If the organization has written procedures or role descriptions, use them as reference points. Authority is easier to manage when it is connected to legitimate responsibilities rather than personal status.
#3. Address the Behavior Privately and Promptly
Do not allow a pattern to continue for weeks while resentment builds. At the same time, avoid correcting the person publicly unless immediate intervention is necessary to protect the work or another employee. A private conversation gives both of you a better chance to discuss the issue without embarrassment, defensiveness, or an audience looking for sides.
Arrange a focused conversation rather than confronting the person in a hallway or sending an angry message. Describe the behavior, explain its practical effect, and state the expectation going forward. Keep the discussion proportionate to the issue. A minor interruption may require a brief correction; repeated undermining may require a more formal meeting.
A useful structure is:
- State what you observed.
- Explain how it affected the work or team.
- Ask for the person’s perspective.
- Clarify the expected behavior.
- Agree on what will happen next.
For example:
In yesterday’s planning meeting, you interrupted me several times and told the team to follow a different deadline after I had confirmed the schedule. That created confusion about which instruction applied. I’d like to understand what led you to respond that way, and I need future concerns about the plan raised with me before directions are changed.
This approach addresses conduct without attacking character.
#4. Listen for Legitimate Concerns Without Surrendering Responsibility
Listening does not mean giving up your decision-making role. The person may have information you missed, a reasonable objection to the plan, or a concern about workload, quality, safety, or fairness. If you dismiss every challenge as disrespect, you may reinforce the very behavior you want to change. People are more likely to accept an authority figure who can distinguish disagreement from defiance.
Ask questions that invite specific information: “What risk do you see in this approach?” “What happened when you tried to raise this concern?” or “What led you to take that action without checking with me?” Then evaluate the answer rather than treating it as a defense that must be defeated.
You can acknowledge a valid point while maintaining the boundary:
Your concern about the reporting deadline is reasonable, and I will review the workload before confirming it. The separate issue is that you changed the deadline without discussing it first. Please bring that type of concern to me before giving the team new instructions.
If the person identifies a real problem in your management, correct it openly. Doing so does not weaken your authority; it demonstrates judgment. The boundary remains necessary even when the original decision needs revision.
#5. Set Specific Expectations and Consequences
General requests such as “show more respect” are difficult to apply and easy to dispute. Translate the concern into behaviors the person can understand and you can observe. Explain how disagreements should be raised, who must approve changes, how quickly concerns should be reported, and what communication is expected in meetings or written updates.
Make the standard practical. For example, the expectation might be that the employee raises objections privately before a decision is finalized, does not issue conflicting instructions to colleagues, and follows an agreed decision unless a new risk requires escalation. If the person disagrees with the decision, they may document the concern or use the established review process, but they may not quietly substitute their own plan.
Explain consequences calmly rather than using threats:
Going forward, please bring proposed changes to me before communicating them to the team. If the pattern continues, I will need to document the incidents and involve the appropriate manager or HR resource under our normal process.
Only mention consequences you are authorized and prepared to follow. Do not promise punishment, removal, or other outcomes you cannot control. Consistent, proportionate follow-through is more credible than dramatic warnings.
#6. Follow Up and Document the Pattern
One conversation may resolve the issue, but you should not assume that it has. Follow up after an agreed period, especially when the behavior affected deadlines, customer service, safety, team morale, or decision-making. A brief check-in can reinforce improvement and identify whether further action is needed.
Keep factual notes about significant incidents. Record the date, what occurred, the direction or expectation that applied, the impact, and how you responded. Include the person’s explanation where relevant. Avoid editorial descriptions such as “was arrogant” or “wanted to undermine me.” Documentation should help another responsible manager understand the situation without relying on your interpretation of motives.
You can summarize an agreement in writing:
Thanks for discussing the project communication issue today. We agreed that you will raise proposed timeline changes with me before communicating them to the team, and I will respond to concerns as promptly as possible. We will review how this is working during our next one-to-one meeting.
This creates a shared reference point and reduces future disputes about what was said. Recognize genuine improvement, but do not overlook a recurrence simply because the person behaved well for one or two days.
#7. Escalate Through the Proper Channel When Necessary
Escalation becomes appropriate when the behavior continues after clear feedback, materially disrupts the team, involves retaliation or harassment, bypasses required controls, or creates a serious risk to operations. It may also be necessary when the person’s role is senior to yours, when authority is shared, or when you lack the power to address the consequences directly.
Before escalating, organize the relevant facts and review any applicable internal process. Speak with your manager, HR, or another designated resource rather than recruiting coworkers into a campaign against the individual. Explain what you observed, what expectations you communicated, what response you received, and what impact continues. Ask for guidance on the next appropriate step.
Escalation should not be framed as “I want this person punished because they do not respect me.” A stronger description is: “The employee has repeatedly issued conflicting instructions after being told not to, which has caused missed handoffs and confusion about accountability. I addressed the behavior on these dates, but it has continued.”
Remain professional after escalation. Do not retaliate, gossip, or make the person’s work unnecessarily difficult. The goal is to restore clear accountability and effective working relationships, not to win a personal contest.
When the Person Is Technically Right but Still Undermines Your Role
A particularly difficult situation occurs when the person’s criticism has merit but their method is disruptive. They may correctly identify a flawed deadline, an inefficient process, or a risk you overlooked. That does not give them unlimited permission to bypass you, embarrass you in meetings, or redirect coworkers without agreement.
Treat the substance and the conduct as separate questions. First, examine whether the criticism requires a change in the decision. If it does, acknowledge that plainly and correct the plan. Second, explain how the concern should have been raised and what boundary applies in future situations. This prevents you from defending a bad decision merely to appear authoritative, while still preserving the reporting structure.
A useful response might be:
You were right that the original timeline did not account for the approval delay, and I have adjusted it. I also need us to address how the issue was handled. Telling the team to ignore the approved schedule created confusion. In future, bring urgent concerns to me immediately, and do not replace a team instruction without confirming the change.
This combination of accountability and humility often produces a stronger result than insisting on authority for its own sake. Your role is not to be correct about everything. It is to make responsible decisions, invite useful information, and ensure that agreed decisions are carried out through a clear process.
Closing Thoughts
Managing someone who does not respect your authority requires more than asserting your title. Start with specific observations, confirm that your responsibilities and expectations are clear, and address the conduct privately and promptly. Listen for legitimate concerns without allowing disagreement to become an excuse for bypassing agreed boundaries. Then document important incidents, follow up consistently, and escalate through the proper process when informal correction does not work. Professional authority grows through clarity, fairness, sound decisions, and reliable follow-through—not through intimidation.