Join UsCEO MastermindAI Leadership MastermindExecutive AI ProgramFractional AI ExecutiveFractional Advisory1:1 Coaching5-Minute Leader
BooksPower Without PermissionAI Leadership Mastermind
PodcastMeet the Team
ResourcesBlogFree Courses5-Minute Leader AcademyFree AssessmentsResearch and DataTeaching PackagesTestimonialsCEO Coaching ReportGuest Post NetworkJoin UsAdd us on Google

Insubordination at Work: What It Is, What It Is Not, and the Three Conversations Before the Document

Insubordination defined for managers, with examples, the four things it is not, the three conversations that come before any document, and what to record.

By Andreas Pettersson, Founder, Leaders ADAPT

It is one of the most searched words in management and one of the most misused. Half the managers who search it are describing an employee who disagreed with them. The other half have a real refusal on their hands and have not yet had a single plain conversation about it.

This page is the manager's side. What insubordination is, the four things it is not, the three conversations that come before any document, and what to write down when it gets that far. It is not legal advice. Your policy and your local employment law decide the formal steps.

I run Leaders ADAPT and wrote the 5-Minute Leader. The Accountability Protocol in it has the three conversations, and most of what gets called refusal in companies is a manager who skipped the first one.

Quick answer: Insubordination is a deliberate refusal to follow a clear, reasonable and lawful instruction from someone with the authority to give it. Disagreeing while complying is not insubordination, nor is asking why, raising a legitimate concern, or doing a task badly. Before any document, three conversations: the correction within 24 hours, the pattern conversation with a date, and the consequence conversation. Then record what a camera would have seen.

Insubordination, defined

Insubordination is a deliberate refusal by an employee to carry out a reasonable and lawful instruction that was clearly given by a person with the authority to give it, after the employee understood it. Every clause in that sentence is a test, and most claimed cases fail at least one.

The general definition comes from military and employment contexts and carries the same three parts everywhere: a legitimate order, understood, refused on purpose.

What it is, and what it is not

Insubordination Not insubordination, though it gets called that
"I was told plainly, I understood, and I am not doing it" Disagreeing with the decision and doing it anyway
Openly refusing a task in front of the team after being asked directly Asking why, or asking for the reason in writing
Ignoring a restated instruction after the consequence was named Raising a safety, legal or ethical concern about the instruction
Telling the manager to do it themselves Doing the task late or badly, which is a performance problem
Not doing something that was implied but never actually said

The right column is where managers lose their best people. The employee who argues in the meeting and then executes the decision is not refusing. She is the person telling you the truth, and if that is the word that comes to mind when someone disagrees, the problem is in the left chair.

The fifth row is the most common. The instruction was never given. It was assumed, hinted at or mentioned once in passing, and the manager is now furious that it was not followed. The clear expectations page is the fix for that, and it comes before anything on this page.

Examples, with the test applied

An employee told on Monday, in a 1:1, to stop sending proposals to clients without review, sends three on Wednesday and says in the stand up that the review step is pointless. Clear instruction, understood, refused on purpose. Yes.

An employee asked to take on the vendor audit replies "no, that is not my job, do it yourself" in front of four colleagues. Reasonable instruction, authority present, open refusal. Yes, and the public setting makes it a serious single incident under most policies.

An employee asked to "keep an eye on the inbox" lets a complaint sit for two days. No clear instruction was ever given. No. A management problem, fixed with a named owner and a handover.

An employee refuses to drive the delivery van because the brake warning light is on. Refusal, but of an instruction that may not be safe. No. Listen.

Boomerang check: does your work stay delegated, or does it come back?

Three questions, scored to the protocol that fixes the leak. The 5-Minute Leader is the four protocols, Delegation, 1:1, Accountability and Rhythm, written down so a manager can run them in about five minutes a day, so tasks stop boomeranging back half done.

Get the 5-Minute Leader or see what is inside the 5-Minute Leader.

The three conversations before any document

The Accountability Protocol I teach has one rule that applies here more than anywhere: a formal step is never the first time the person hears about the problem. Three conversations come first, each one short, each one dated in your notes.

One, the correction, within 24 hours. In private, in the Warm but Firm shape. "I am raising this because I want you here and doing well. On Wednesday you sent three proposals without review after we agreed on Monday that nothing goes out unreviewed. The agreement stands. Next time it happens we are having a different conversation. What do you need from me to make this work?" One minute. Then note the date.

Two, the pattern conversation, if it repeats. "This is the second time. I have noticed a pattern: when we agree a process, it holds for a day. From now on, every proposal goes through review, and if one does not, it is documented. Can you commit to that?" Note the date. The how to hold employees accountable page has the full script, including the three kinds of pushback.

Three, the consequence conversation, which is the written warning delivered in person, with HR if your policy requires it. By now the employee has heard it twice, by date, and the document is a record of a conversation, not an ambush. The how to write up an employee page has the six part template.

If the single incident is serious enough, open refusal in front of the team, say, your policy may call for the document at step one. Even then, the conversation that delivers it follows the same shape.

The Chronic Complainer and the Dodger

Two of the three conversations the Accountability Protocol says managers avoid most sit right next to refusal without being it. The Chronic Complainer raises problems and never solutions, which is exhausting and is not refusal. The Dodger explains rather than owns, which is frustrating and is not refusal. Both need the pattern conversation, not the discipline process, and a manager who reaches for the discipline word with either of them has skipped a step. The difficult conversations with employees page has both scripts.

What to record, and how

Date, time and place. The exact instruction, who gave it and when, ideally quoting your own words. The employee's exact words or actions in response. Witnesses by name. The date of each earlier conversation and what was agreed.

Write what a camera would have recorded. "Refused to attend the 9am stand up on Tuesday 4th after being told on Monday 3rd that attendance was required, saying 'I do not do stand ups'" is a record. "Insubordinate attitude" is an opinion, and it is the sentence the employee's representative will read aloud first.

Then stop writing and follow your policy. HR, local law, any union agreement and the contract decide what happens next, and they are not on this page.

The three conversations, scripted

Most of it is a conversation that was skipped, and the Accountability Protocol in The 5-Minute Leader is the three conversations with the words in. I wrote the book after scaling a company to more than 150 people and watching managers go from silence to a formal warning with nothing in between, every time. Four protocols, Delegation, 1:1, Accountability and Rhythm, each run in about five minutes a day, so the correction happens while it is small and the document stays rare.

The Accountability Protocol holds Warm but Firm, the three conversations managers avoid most, the Dodger, the Unprepared and the Chronic Complainer, and the answer to each of the three kinds of pushback, including the one where the employee says the instruction was unreasonable.

There is one sentence in it for the moment an employee says "that is not my job", and it is not the sentence most managers reach for.

Get the 5-Minute Leader

Insubordination FAQ

What is insubordination at work?

Insubordination is a deliberate refusal to follow a reasonable and lawful instruction from someone with the authority to give it, after the instruction was clearly given and understood. All three parts matter: the instruction was reasonable, it was clear, and the refusal was a choice. Missing any one of the three, it is something else, usually a management problem.

What are examples of insubordination?

An employee told plainly to stop sending client emails without review, who sends three more the same week and says so. A team member who, asked in a meeting to take an action, says "no, do it yourself" in front of the room. Someone who, after the policy is restated and the consequence named, ignores it again. Each is a clear instruction, understood, and refused.

What is not insubordination?

Disagreeing with a decision while still carrying it out. Asking why. Raising a safety, legal or ethical concern. Refusing an instruction that was never actually given, only implied. Doing the task badly, which is a performance issue. Managers who label disagreement as insubordination lose the people who were telling them the truth.

How should a manager handle insubordination?

Check first that the instruction was clear, reasonable and understood, because most cases fail here. Then have the small conversation within 24 hours, in private: the behavior, the effect, the expectation, the consequence next time. If it repeats, the pattern conversation with a date. Only then the written warning, with HR, following your policy and local law.

Can you fire an employee for insubordination?

In many places yes, and in some cases for a single serious incident, but the rules depend on country, state, contract and any union agreement, and on whether the instruction was lawful and the process fair. This page is the manager's side of the job, not legal advice. Before any dismissal, involve HR or employment counsel and follow the documented steps.

How do you document it?

Date, time, place, the exact instruction given and by whom, the employee's exact words or actions in response, any witnesses, and the date of each earlier conversation about it. Write what a camera would have recorded, not a judgment. "Refused to attend the 9am stand up after being told attendance was required on Monday 3rd" is a record. "Has a bad attitude" is not.

Run the three part test before you use the word

Was the instruction clear, reasonable and actually given. Did the person understand it. Did they refuse on purpose. If any answer is no, it is not insubordination, and the fix is on your side of the desk. If all three are yes, have the first conversation today, in private, and note the date. The document comes third, never first.

Which instruction did you assume was clear that you never actually said out loud?

Get the three conversations with the words in.

Leadership insights, straight to your inbox

Practical protocols from a former Canon CEO. No fluff, unsubscribe anytime.

Andreas Pettersson

Andreas Pettersson

Former Canon CEO. Founded and exited Arcules, an AI company backed by Canon and Milestone. Today he coaches CEOs and executives through Leaders ADAPT.

More Posts

Free Leadership Profile & Style Assessments