From PIP to Manager’s Exit – My Journey
So, let me tell you how a simple performance improvement plan (PIP) turned into a full‑blown battle that finally saw my manager leaving the company. I’m not naming anyone, because the whole thing was posted anonymously on Blind, but the events are exactly as they happened.
It all started when I raised a concern about a project that had been delayed for months. Everyone in my team was sure the delay was because my manager kept pushing the timelines without any realistic plan. I politely pointed this out in a team meeting and dropped a short email to the manager asking for clarification. A few days later, I found myself on a PIP. In my mind, it felt like a classic retaliation move – you speak up, you get punished.
What the PIP Looked Like
A PIP is basically a formal document that says, ‘You’re not meeting expectations, improve or we’ll part ways.’ In my case, the document listed a few vague points: “underperformance on X” and “needs improvement in communication.” The weird part was that just three weeks earlier the same manager had sent me a Slack message saying, “Great work on X! Keep it up.” I thought to myself, “Are you serious?” It felt like a bait‑and‑switch, and I decided I wasn’t going to sit quietly.
Usually people just accept the PIP, try to improve, and hope for the best. But not me. I chose to fight back, because I had seen other colleagues get stuck in similar situations and never speak up. I wanted to make sure the company knew I wasn’t being unreasonable.
Collecting the Evidence
First thing I did was go through my Slack history, emails and any other written communication. It took me about two weeks of early mornings and late nights, but I managed to pull out a few key messages:
- A Slack message from the manager praising my work on the very task that later appeared in the PIP as a failure.
- A chain of emails where senior leadership asked for an update on the delayed project, and the manager kept sending vague replies.
- Notes from a one‑on‑one where the manager told me I was doing well, then suddenly turned around and said I was underperforming.
I also reached out to two former teammates who had left the company a few months earlier. Both of them told me they had experienced the same kind of pressure from the same manager. One of them even aGreed to provide a written statement supporting my claim. Having a witness, even if they’re no longer in the firm, added weight to my case.
Taking It to the Ethics Team
Instead of going straight to HR, I decided to file a complaint with the company’s ethics team. In my experience, the ethics team is a bit more independent, and they tend to look at the bigger picture – retaliation, harassment, that sort of thing. I wrote a concise but detailed email, attaching the Slack screenshots, email threads and the statement from my former colleague.
The email went something like this: “I’d like to raise a concern about possible retaliation relating to a PIP I received. Below is a timeline of events, along with evidence that suggests the PIP was issued shortly after I raised a legitimate project‑delay issue.” I kept the tone factual, avoided any emotional language, because I knew the ethics team would scrutinise every word.
After sending it, I waited. Usually you might hear back within a few days, but this time I got a reply after a week asking for a brief meeting to discuss the matter further. The ethics team said they’d also forward the case to a skip‑level manager – the manager’s manager – for a neutral review.
Escalating to the Skip‑Level Manager
Now, this was a tricky part. I had to write another email, this time to the skip‑level manager, who I didn’t know personally. I kept the email short, factual, and respectful. I laid out the timeline, attached the same evidence and asked for a quick look‑over. I also mentioned that the manager’s recent behaviour could expose the company to legal risk if it’s deemed retaliatory.
Honestly, I was nervous. In most Indian offices, you don’t usually email a senior person directly unless you’re encouraged to do so. But I felt I had no other choice. I sent the email, and a couple of days later, I got a reply acknowledging the receipt and promising to look into it.
Within a month of raising the complaint, the manager was placed on what the company called a “management coaching plan”. I heard this through informal channels – a friend in the same department mentioned it during a coffee break. The coaching plan, as far as I understand, is a remedial measure where the manager goes through leadership training while being closely monitored.
The Manager’s Exit
Six weeks after the initial PIP, the manager left the firm. The official reason was “personal reasons”, but many of us who were close to the situation knew it was linked to the coaching plan and the ongoing investigation. I didn’t hear any formal announcement about the departure, which is typical in large tech firms – they just update the org chart and move on.
My own PIP was rescinded shortly after the manager’s exit. The HR team sent me a note saying the performance concerns were unfounded and that I could continue in my role without any further action. I felt a mix of relief and validation – the system had finally corrected itself, at least in my case.
Reactions on Blind and Beyond
The post I made on Blind quickly gathered dozens of comments. Some people warned that it was a one‑off situation, that not everyone would get such a clean outcome. Others cheered me on, saying it was a sign that employees should not just roll over when they’re PIPed.
One comment read, “Everyone on here just rolls over when they get PIPed… Nah. I chose violence.” Another user wrote, “Hats off! Hope the manager learned a lesson about misusing authority. If more people start doing this, half the managers at Amazon will be fired for all their horrible acts of throwing people under the bus.” These reactions were a mix of humor, frustration and genuine hope for change.
There were also more measured voices. Some pointed out that the evidence had to be solid, that you can’t just claim retaliation without proof. A few even suggested that companies should have clearer policies about PIPs to avoid them being used as a weapon.
What This Means for Tech Workers in India
From my experience, a few key take‑aways emerged for anyone working in the Indian tech space:
- Document everything. Keep Slack messages, emails and any written feedback. It may feel tedious, but it can save you later.
- Don’t be afraid to use internal ethics or compliance teams. They are often more neutral than HR when it comes to retaliation claims.
- Build a small network of supportive colleagues. Even a single former teammate willing to give a statement can strengthen your case.
- Stay professional in your communications. Stick to facts, dates and evidence. Emotional language can be used against you.
- Know that outcomes vary. Not every PIP can be overturned, but a well‑structured case raises the cost for a company to ignore possible legal risk.
In most Indian offices, hierarchy is strong and many employees feel they have to accept decisions without question. My story shows that, with the right approach, you can push back without burning bridges.
Broader Debate: Are PIPs Being Misused?
There is an ongoing debate in the tech community about the purpose of performance improvement plans. Ideally, they are meant to help an employee improve their skills, not to punish them for speaking up. However, several anecdotes suggest that some managers use PIPs as a retaliatory tool.
Legal experts in India have warned that if an employee can prove a PIP was issued in bad faith, the company could face costly litigation. That’s part of why many large firms now have internal checks, like ethics hotlines, to review such cases. Still, the system isn’t perfect – smaller startups often lack a dedicated ethics function, leaving employees more vulnerable.
My experience highlights the importance of transparency. When a PIP is linked to a concrete performance metric, and when there is clear documentation of achievements, it becomes harder for a manager to use it as a weapon. Conversely, vague, generic PIPs are ripe for misuse.
Final Thoughts
Looking back, I’m glad I didn’t just accept the PIP and fade into the background. It took a lot of effort – pulling together evidence, writing precise emails, and dealing with the anxiety of a possible backlash – but it eventually paid off. My manager left, my own record was cleared, and I learned a valuable lesson about standing up for myself.
For anyone out there facing a similar situation, my advice is simple: keep your cool, gather facts, use the right channels, and remember that the company is also protecting its reputation. Companies don’t care much about loyalty; they care about risk. If you can show them that the risk is real, they will act.
And for the managers reading this – treat performance plans as tools for development, not weapons. A fair, transparent process will keep your team motivated and protect you from potential fallout.
