Insubordination is an employee’s deliberate refusal to follow a lawful and reasonable instruction from someone with the authority to give it. It also covers open defiance of that authority, such as ignoring a direct order, walking away from a manager mid-conversation, or publicly challenging a supervisor’s right to direct the work. The key word is deliberate. A genuine misunderstanding, a missed deadline, or a respectful disagreement is a different problem, and treating it as insubordination usually makes the situation worse.
For managers, the distinction matters because the response is different in each case, and because discipline records around insubordination can surface later in disputes over termination. This guide covers what insubordination is, what it is not, the examples that show up most often, why it spreads when it goes unaddressed, and the steps leaders use to handle it fairly.
What does insubordination mean?
At its core, insubordination is the willful disregard of legitimate authority in the workplace. Three elements usually need to be present:
- A clear, lawful, and reasonable instruction. The direction has to be something the employee can actually understand and act on, within the scope of their role, and legal.
- Authority to give it. The instruction comes from a manager, supervisor, or someone the organization has authorized to direct that work.
- A deliberate refusal or act of defiance. The employee understands the instruction and chooses not to comply, or openly challenges the authority behind it.
When all three are present, you are likely looking at insubordination. When one is missing, you are probably looking at something else, and that distinction shapes everything that follows.
What insubordination is not
This is where most managers get into trouble, so it is worth being precise. The following situations are commonly mistaken for insubordination and should be handled as separate issues:
- Poor performance. An employee who is trying but falling short has a capability or clarity problem, not a defiance problem. That calls for a performance conversation rather than discipline.
- A single missed instruction. Forgetting a task or misreading a request is a communication gap.
- Respectful disagreement. An employee who voices a concern and then still does the work is engaged, not insubordinate. Punishing this teaches people to stay silent.
- A lawful refusal. Declining to do something illegal, unsafe, or outside the bounds of employment law is protected in many cases, not insubordinate.
- Protected activity. Raising concerns about discrimination, safety, or wage issues, or discussing working conditions, can carry legal protection depending on jurisdiction.
A simple test helps: did the employee understand a reasonable, lawful instruction from someone with the authority to give it, and choose to defy it? If yes, treat it as insubordination. If the honest answer is unclear, slow down and gather facts before labeling it.
Common examples of insubordination
Insubordination ranges from loud and obvious to quiet and corrosive. Recognizing the quieter forms early is what keeps a single incident from becoming a pattern.
Direct and visible:
- Flatly refusing a clear, reasonable task after being asked directly.
- Walking out of a meeting or off a shift after being given an instruction.
- Challenging a manager’s authority in front of the team or customers.
- Using hostile or abusive language toward a supervisor.
Quiet and easy to miss:
- Agreeing to a task and then repeatedly not doing it.
- Going around a manager to undermine a decision after it has been made.
- Selectively following only the instructions the employee likes.
- Slow-walking work as a form of passive refusal.
The quieter behaviors do the most damage to morale because they are harder to name and easier to excuse. For a fuller breakdown of the patterns leaders tend to overlook, see the companion piece on insubordination examples managers overlook.
Insubordination vs. a bad attitude
A bad attitude is a tone problem. Insubordination is an action problem. An employee can have a sour disposition and still do everything that is asked of them, and an employee can be perfectly pleasant while quietly refusing to comply. Discipline rests on conduct you can describe and document, so the question to ask is always about what the person did or did not do, rather than how they seemed to feel. Frame your records around observable actions, instructions given, and responses taken.
Why insubordination spreads when it goes unaddressed
When a clear act of defiance goes unanswered, the rest of the team draws a quiet conclusion: the rules are optional, and following them is for people who lack leverage. That perception erodes accountability faster than almost anything else a manager deals with. The cost shows up as slower execution, resentment among the people still pulling their weight, and a gradual shift in what the team treats as normal. It is one of the warning signs of a culture under strain. Addressing insubordination promptly and proportionately is less about the individual incident and more about protecting the standard everyone else is being asked to meet.
How managers should respond to insubordination
A measured, consistent process protects the team, the organization, and the employee’s right to fair treatment. The following sequence reflects common best practice. Always align it with your own organization’s policies and, where the stakes are high, with HR and legal guidance.
1. Pause and confirm the facts
Before acting, separate what you observed from what you assumed. Confirm that a clear, lawful instruction was given, that the employee understood it, and that the refusal was deliberate. Acting on a misread situation undermines your credibility and can create legal exposure.
2. Address it privately and promptly
Handle the conversation away from the team. Describe the specific behavior, reference the instruction that was given, and give the employee a genuine chance to explain. Sometimes what looked like defiance has a reason you did not have, and the private conversation is where that surfaces.
3. Be clear about the expectation and the impact
State the standard plainly, explain why it matters, and describe what needs to change. Keep the focus on the conduct and the work, and keep your own tone steady even if the employee’s is not.
4. Document the incident
Write down the date, the instruction, the behavior, what was said in the conversation, and the agreed next steps. Stick to factual, observable detail. Good documentation protects everyone and is often what disputes later turn on.
5. Apply consequences consistently
Follow your organization’s progressive discipline process, and apply it the same way you would for anyone else in the same situation. Inconsistency is both unfair and legally risky.
6. Follow up
Check in after the conversation. Acknowledge genuine improvement, and continue the process if the behavior repeats. Follow-through is what signals that the standard is real.
A note on documentation and write-ups
If your process reaches a formal write-up, keep it grounded in facts: the instruction given, the date and setting, the specific response, any prior conversations, and the expectation going forward. Avoid characterizations of the person’s character or mood, and describe conduct instead. Clear, behavior-based records are easier to defend and fairer to the employee.
When refusing an instruction is the right call
It is worth stating directly: not every refusal is misconduct, and treating lawful refusals as insubordination can expose an organization to real liability. An employee may have grounds to decline an instruction that is illegal, that poses a genuine safety risk, or that falls outside the scope of their employment. Refusals connected to protected activity, such as reporting harassment or discussing pay, can carry legal protection that varies by jurisdiction. When a refusal touches any of these areas, treat it as a signal to consult HR or legal counsel rather than as a disciplinary matter.
This article provides general information for managers and is not legal advice. Employment law varies by location, so check your organization’s policies and consult a qualified professional before acting on a specific situation.
Frequently asked questions
What is the simplest definition of insubordination?
Insubordination is when an employee deliberately refuses to follow a lawful, reasonable instruction from someone with the authority to give it, or openly defies that authority.
Is insubordination the same as a bad attitude?
No. A bad attitude is about tone and demeanor, while insubordination is about conduct. An employee can have a poor attitude and still comply, and discipline should be based on documented behavior rather than mood.
Can an employee be fired for insubordination?
In many cases yes, particularly where there is a clear instruction, deliberate refusal, and a documented process. Because wrongful-termination claims often hinge on consistency and documentation, organizations typically involve HR and follow a progressive discipline policy.
Is refusing an unsafe or illegal order insubordination?
Generally no. Declining to do something illegal or genuinely unsafe is often protected, and so is refusing work tied to protected activity. These situations call for HR or legal review rather than discipline.
How should a manager document insubordination?
Record the date, the specific instruction, the employee’s response, what was discussed, and the agreed next steps, using factual and observable language. Avoid judgments about the person and focus on what happened.
What is the difference between insubordination and poor performance?
Poor performance is an inability to meet a standard despite trying. Insubordination is a deliberate refusal to comply with a reasonable, lawful instruction. The first is a capability issue, the second is a conduct issue, and they call for different responses.
