Skip to main content

Never sign a PIP. Here’s why.

http://gengwg.blogspot.com/I alluded to this topic in Friday’s post, and now I’ll address it directly. This search query comes to my blog fairly often: “should I sign a PIP?” The answer is no.

Why? Chances are, performance doesn’t mean what you think it does. Most people think of “performance improvement” as something well-intended, because they take performance to mean “how good I am at my job”. Well, who doesn’t want to get better at his or her job? Even the laziest people would be able to get away with more laziness if they were more competent. Who wouldn’t want to level up? Indeed, that’s how these plans are presented: as structures to help someone improve professional capability. However, that’s not what “performance” means in the context of a employment contract. When a contract exists, non-performance is falling short of an agreed-upon provision of the contract. It doesn’t mean that the contract was fulfilled but in a mediocre way. It means that the contract was breached.

So when someone signs a PIP, he might think he’s agreeing that, “Yeah, I could do a few things better.” That’s not what he’s actually saying, at least not to the courts. He’s agreeing to be identified as a non-performing– again, in the legal sense of the word– employee, in the same category as one who doesn’t show up or who breaks fundamental ethical guidelines. Signing a PIP isn’t an admission that one could have been better at one’s job, but that one wasn’t doing one’s job. Since white-collar work is subjective and job descriptions are often ill-defined, making the binary question of professional and contractual performance difficult to assess in the first place, this sort of admission is gold for an employer looking to fire someone without paying severance. The employer will have a hell of a time proving contractual non-performance (which is not strictly required in order to fire someone, but makes the employer’s case stronger) without such a signature, given that most white-collar work has ill-defined requirements and performance measures.

Managers often claim that signing such paperwork only constitutes admission to having read it, not agreeing to the assessment. Even if true, it’s still a bad idea to sign it. This is now an adversarial relationship, which means that what makes the manager’s work (in the firing process) easier makes your life worse. Verbally, you should say “I agree to perform the duties requested of me, and to make the changes indicated, to the best of my ability, but there are factual inaccuracies and I cannot sign this without speaking to an attorney.” If you are pressed to sign, or threatened with termination, then you may sign it, but include the words “under duress”. (The shorthand “u.d.” will not suffice.) What this means is that, since you were threatened with summary termination, you were not free to decline the PIP, and therefore your signature is meaningless.

Whether you sign the PIP or not, you will probably be fired in time, unless you get another job before the process gets to that point. Not signing it doesn’t make it impossible for them to fire you. It only makes it somewhat harder. So why is it harmful to sign it? You want two things. First, you want time. The longer you have to look for a new job while being employed the old company, the better. If your manager sees you as a risk of messy termination, he’s more likely to let you leave on your own terms because it generates minimal work for him. PIPs are humiliating and appear to be an assertion of power, but they’re an exhausting slog for a manager. Second, you want severance if you don’t find a job in time and do get fired. Severance should never be your goal– non-executives don’t get large severances, so it’s generally better for your career and life to get another job– but you shouldn’t give that away for free.

There isn’t any upside to signing the PIP because, once one is presented, the decision to fire has already been made. A manager who genuinely wants to improve a person’s performance will communicate off the record. Once the manager is “documenting”, the relationship’s over. Also, people very rarely pass PIPs. Some people get the hint and leave, others fail and are fired, and in the remainder of cases, the PIP is ruled “inconclusive”, which means “not enough evidence to terminate at this time”. That’s not exactly an endorsement. For a PIP to be passed would require HR to side with the employee over management, and that will never happen. If the employee is under the same manager in 6 months, there will be another PIP. If the employee tries to move to another team, that will be almost impossible, because a “passed” PIP doesn’t mean exoneration. The reputation for instability created by a PIP lingers on for years. What I am essentially saying here is that, once a PIP appears, you should not sign it for the sake of maintaining a professional relationship. There is no relationship at that point.

Signing the PIP means you don’t know how to play the termination endgame. It means that you have no idea what’s happening to you, and you can be taken advantage of.

This said, there’s a way of not signing it. If you appear to be declining to sign out of bitterness or anger, that doesn’t work in your favor. Then you come off as childish. Childish people are easy to get rid of: just put them in increasingly ridiculous circumstances until they lose their cool and fire themselves by doing something stupid, like throwing a stapler at someone. The image you want to project is of a confident, capable adult– one who will not sign the PIP, because he knows it’s not in his advantage to do so, and who knows his rights under the law. This makes you intimidating. You don’t want to frighten adversaries like this– a frightened enemy is dangerous unpredictable– but you do want to intimidate them, so they get out of your way.

There’s a lot more to say about PIPs, which are dishonestly named processes since their real purpose is to create a paper trail to justify firing someone. That I’ll cover in a future post. For now, I think I’ve covered the most important PIP question. Don’t sign the fucking thing. Be professional (that’s more intimidating than being bitter) but decline to sign and, as fast as you can, get another job. If you see a PIP, moving on is your job.

Comments

Popular posts from this blog

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into ...

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checkin...