|
The whole point of having line managers write PIPs together with employees is to have these vaguely valid-seeming reasons on PIPs. There is, however, also a reason the PIP process got initiated. It is never the line manager that initiates a PIP process (you'd have to have exceptionally poor performance for that, frankly I wonder if they even have the power to do so). You get onto a PIP because some external-to-the-team person, maybe a TPM, maybe a higher up manager, complained about you. They don't always explain why to your manager, in fact, it's probably generally a smart move for them NOT to say why (frankly, some people complain to your manager because you came to the office with untied shoelaces). When that happens (maybe your manager gives you two or three "strikes"), your manager comes to you and writes a PIP. What that PIP will NEVER say is "make X not complain about you anymore". It will say "write more code", "take ownership of bugs", "take more feedback into account", because, as you point out, HR would freak if it said "do what X says". Plus, of course, if at all possible your manager will try to not have you work with that complaining person anymore. Which would make such a PIP redundant/impossible. PIPs are always because someone asked for them. Maybe (hopefully) indirectly, and not always (one hopes never, but ...) for the reason "quota", but essentially always because someone asked for them. PIPs never say that, so they never give the real reason. The point is indeed to scare you into being "more cooperative". HR kind-of tells the truth: the point of a PIP is to make you a better employee. It really is. All else equal, they want it to go away as much as you do. But if it doesn't go away, the point of a PIP is to fire you, safely, without getting sued afterwards, without HR having to do any work at all. |