Insubordination Warning Letter Sample

Dealing with insubordination is pretty straightforward, and is down to 3 basic steps. Talking, warning and termination, and can be rather pleasant if it ends at step 1. However, life is not a textbook, and insubordination can be difficult to prove at times, when the insubordination stems from passive-aggressive behavior. Regardless of the covertness, or overtness, of the insubordination, the person must be handed a formal warning letter, in the hopes that they would take heed, before considering termination, as this behavior if tolerated, will be the downfall of the company.

A potentially good employee could turn into a rotten egg, unless you can get through to them, and talk reason into them, if they are someone you could talk reason into. Try involving the insubordinate employee in the process which is causing the problem, perhaps it is not the authority they are challenging, but the fact that it was forced on them.

Here’s a sample to assist you with your ordeal:

 

Insubordination Warning Letter Sample

 

Dan Hanson
Project Manager
Startup Apps, Inc.
4558 Park Street
San Jose, CA 95134

March 12, 2017

John West
Mobile App Developer
Startup Apps, Inc.

 

Dear Mr. West:

I have noticed that you have not yet started writing SRS documents as per the new rules that were introduced by the Quality Assurance department last month, despite undergoing the new SQA SRS Rules & Guidelines training, in which you performed rather impressively. I would like to know why you still have not implemented the new rules in your work, and also to ensure we are on the same page regarding the importance of enterprise-wide implementation of the new set of rules, for competing in the startup apps industry.

Not only would I like you to help me work out the best way to implement these new rules, I would actually like to put you in charge of the implementation.

Let’s talk about this in detail, I am available from 3:00 to 5:00 pm this Friday, (date), and would like to get this solitary kink ironed out before the next QA Audit.

It is up to you to call for a second letter, or consider this your first and last warning. As you know, a third strike will lead to termination.

I look forward to seeing you in my office Friday at 3:00, and I am hoping we could talk things through positively, as you are one of my brightest developers and I would hate to see you go.

 

Regards,

(Signature)
Dan Hanson
Project Manager
Startup Apps, Inc.
4558 Park Street
San Jose, CA 95134








Last updated on