In a workplace, insubordination is rarely just about bad manners. More often, it is the point where disagreement turns into a deliberate refusal to follow a lawful, reasonable instruction, and that distinction matters for every manager, team leader, and supervisor. In this article I break down the clearest workplace examples, explain where the boundary lies, and show how to handle the issue without turning a correctable problem into a bigger disciplinary case.
The clearest cases are deliberate refusal, repeated defiance, and unsafe pushback
- Not every argument with a manager is insubordination; the instruction has to be lawful, reasonable, and relevant to the job.
- Clear cases usually involve refusal, open challenge, or repeated non-compliance after the instruction has been restated.
- Health and safety concerns, unlawful requests, or missing training can make a refusal justified rather than misconduct.
- In the UK, serious insubordination can become gross misconduct, but only after a fair process.
- The way a supervisor responds matters: a rushed, emotional reaction often makes the problem worse.
What counts as insubordination in a workplace
I usually separate three behaviours: refusing a direct instruction, openly defying authority, and undermining a manager in a way that stops work getting done. The instruction itself has to be lawful, reasonable, and within the person’s role; if it is not, the problem may sit with management rather than with the employee.
Acas treats insubordination as misconduct, and serious cases can become gross misconduct. That does not mean every sharp tone or disagreement deserves discipline. It means I look for intent, repetition, and impact on the work before I label the behaviour.
- Refusal means the employee has clearly been told what to do and chooses not to do it.
- Defiance means the person challenges the instruction in a way that blocks the work or undermines authority.
- Pattern matters because repeated non-compliance usually creates more risk than a single bad moment.
That definition becomes much easier to use once you compare it with real workplace behaviour, so I move next to the situations managers actually encounter.
Practical insubordination examples managers actually see
These are the situations I see most often in supervision and disciplinary conversations. Some are obvious, others are subtle, but they all share the same core problem: the employee is choosing not to follow a lawful and reasonable instruction.
| Example | Why it matters | What it often looks like in practice |
|---|---|---|
| Refusing an assigned task | It is the clearest form of non-compliance when the task falls within the role. | A staff member says, “I am not doing that,” after being told to complete a report, prepare a handover, or serve on a rota. |
| Ignoring a safety instruction | This can quickly become serious because it affects people, not just output. | An employee refuses PPE, skips a lockout step, or keeps working after being told to stop for a safety check. |
| Walking out of a briefing or supervision meeting | It cuts off communication and makes it harder to manage performance or risk. | Someone leaves the room mid-conversation after being given a correction or a new instruction. |
| Openly challenging authority in front of the team | Even when the message is emotional rather than explicit, it can damage credibility fast. | Comments such as “You do not know what you are doing” or mocking a manager’s decision in front of colleagues. |
| Repeatedly “forgetting” instructions | One missed task can be error; repeated failure after confirmation looks more deliberate. | The employee nods, confirms the task, and then does nothing until chased again and again. |
| Refusing to follow a policy or process | This is especially relevant in public-sector work where procedures protect fairness and compliance. | A member of staff declines to use the agreed reporting route, timekeeping process, or approval chain. |
What I watch for is not just the language used, but the effect. A rude remark can be unpleasant without being insubordination; a deliberate refusal that blocks service delivery is a different matter entirely. In a local authority, school, or NHS team, that distinction matters because the cost of delay is often felt by the public, not just the manager.
The harder cases are the ones where the employee says no for a reason that may actually be legitimate, and that is where good leadership has to be sharper than instinct.
When refusal is justified instead of insubordinate
I would be cautious about calling something insubordination if the instruction is unsafe, unlawful, unclear, or outside the person’s remit. A supervisor can still expect professionalism, but the first job is to check whether the instruction itself is sound.
- Health and safety risk is the most obvious exception. A worker who refuses to ignore a safety rule is raising a legitimate concern, not necessarily defying authority.
- Unlawful or unethical instructions should never be treated as simple disobedience. If someone refuses to falsify a record, mislead a client, or ignore a compliance rule, I would investigate the instruction itself.
- Missing training or equipment can make a refusal reasonable. People should not be punished for declining work they have not been shown how to do safely.
- Contract or role boundaries matter too. If a task is genuinely outside the job, the answer may be redeployment, clarification, or consultation rather than discipline.
- Protected issues such as discrimination, harassment, whistleblowing, or a request for reasonable adjustment need careful handling before any disciplinary step is considered.
The cleanest leadership move is to separate the issue of compliance from the issue of legitimacy. If the instruction is flawed, fix the instruction. If the instruction is valid and the refusal is deliberate, then the supervision issue is real and needs a proportionate response.
That leads directly to the part many managers skip under pressure: the process.
How I would handle it as a supervisor
When someone pushes back, I would not start with punishment. I would start with clarity, because clear instructions and clear records solve more problems than confrontation does.
- Restate the instruction clearly and make sure the person understands what is being asked, by when, and why.
- Ask for the reason behind the refusal. Sometimes the issue is workload, confusion, stress, or a genuine concern that can be resolved quickly.
- Record the facts rather than the emotion. Write down what was said, who was present, and what instruction was given.
- Investigate before deciding. Good practice is to make a reasonable investigation and use a fair disciplinary procedure.
- Match the response to the conduct. Coaching may be enough for a first lapse; repeated defiance may justify a warning; serious or wilful refusal can move into gross misconduct.
The Acas Code can matter here, and awards may be adjusted by up to 25% when it is unreasonably ignored. In plain English: even a strong case can be weakened by a sloppy process.
I also keep the tone calm and private whenever possible. In public-sector teams, disciplinary drama spreads quickly, and the damage to trust can outlast the original incident if a supervisor handles it carelessly.
Once you handle the moment properly, the next issue is the wider impact on the team.
What repeated defiance does to a team and a public service
One unresolved incident can be awkward. Repeated defiance changes the culture.
- It weakens fairness because colleagues notice when one person is allowed to ignore rules that everyone else follows.
- It slows service delivery when tasks are delayed, handovers fail, or a supervisor has to redo work that should already be done.
- It reduces trust in leadership because a manager who cannot enforce reasonable instructions starts to lose authority.
- It raises operational risk where safety, compliance, safeguarding, or confidential information is involved.
- It encourages copycat behaviour because once one person gets away with it, others test the boundary too.
In a council office, a school, or an NHS setting, that cost is not abstract. It can mean slower responses to residents, missed handovers, complaints from service users, or extra strain on colleagues who are still doing the job properly. That is why I treat insubordination as a leadership issue first and a disciplinary issue second.
The useful question is not “How do I punish this?” but “How do I stop this from becoming normal?”
The line I keep in mind when authority is challenged
My rule is simple: if the instruction was lawful, reasonable, and clear, then a deliberate refusal is a management issue that needs action. If the instruction was unsafe, unclear, or outside policy, then the manager needs to fix the instruction before reaching for discipline.
- Be specific about what was asked, by whom, and when.
- Be proportionate in the response, because not every conflict deserves a formal warning.
- Be consistent across the team, or the standard stops meaning anything.
Handled well, these situations become a useful reset: expectations are clearer, boundaries are firmer, and the team sees that authority is being exercised with judgement rather than ego. Handled badly, the same incident can turn into resentment, grievance, and a culture where defiance is treated as normal.
