Microsoft PIP: What It Means and How to Respond

At most companies, performance problems arrive gradually. Feedback conversations, a rough review, a sense that expectations are shifting. At Microsoft in 2025, the formal process can arrive all at once.

A Performance Improvement Plan (PIP) at Microsoft now works differently than it did three years ago. Under the process formalized by Chief People Officer Amy Coleman in April 2025, the moment a PIP is handed to you, a five-day clock starts. Before that clock runs out, you face a binary decision: take approximately 16 weeks of base pay as a lump sum and leave immediately, or decline the money and attempt the improvement plan. Once you decline the offer, it's permanently off the table.

This structure is not accidental. Understanding what it's designed to do changes how you respond to it.

---

What Microsoft Calls a PIP

Microsoft doesn't have a single branded name for its formal performance management process. The terminology has varied by org, era, and who's talking.

"PIP" is the informal industry term now used most commonly in engineering communities and on Team Blind, where Microsoft employees are verified by company email. "CAP" (Corrective Action Plan) appears in older documentation from legacy orgs like Windows and Office. Same process, older label, less common in newer divisions.

Before formal PIPs became widespread, Microsoft engineers described something called "PIPLite": an informal, manager-driven period of documented scrutiny that preceded a formal process. PIPLite isn't an official HR designation. It's community shorthand for a recognizable pattern: reduced scope, pointed written feedback, a manager quietly building a paper trail before involving HR.

The acronym that matters most right now is GVSA (Global Voluntary Separation Agreement). This is the severance offer presented at the moment of PIP initiation. It defines the financial terms of the binary choice you'll face.

One more term worth knowing: "Good Attrition." Microsoft tracks performance-based departures as a positive workforce metric at the executive level, per reporting by Business Standard. High performers who leave voluntarily are classified as "Regrettable Attrition." Low performers exited via GVSA or PIP failure are classified as "Good Attrition." Managers are tracked on this metric. That structural reality explains a lot about how the process is run.

---

How the Connects System Gets You Here

Microsoft's performance management runs on a semi-annual system called Connects. (The Microsoft Connects performance review guide covers the full cycle in detail.) What matters for understanding a PIP is what happens inside the manager assessment layer, specifically a classification system that employees are not told about directly.

Managers use four confidential impact descriptors, leaked to HRKatha and confirmed in Amy Coleman's April 2025 announcement to managers. Employees see a numeric reward outcome on a 0–200 scale; these descriptors explain the label their manager applied internally:

Descriptor	Meaning
Exceptional Impact	Above and beyond expectations
Successful Impact	Meeting expectations
SLITE: Slightly Lower Impact Than Expected	Below bar; needs attention
LITE: Lower Impact Than Expected	Significantly below bar; PIP territory

The descriptor labels are confidential. Managers are instructed not to use the acronyms SLITE and LITE with employees. What you see is your annual reward number.

The reward scale maps to practical consequences:

Reward score	Outcome
0	Immediate termination
~60	Triggers PIP or GVSA offer
~100	Standard ("Successful Impact")

If your rewards number was low and your manager's communication changed in the weeks after, you're likely in SLITE or LITE territory even if no one has used those words.

A note on "Disconnected" terminology. Engineers in Microsoft communities sometimes reference "Disconnected" or "Occasionally Disconnected" ratings as precursor warning signals. These aren't formal descriptor names. They were informal manager language from older Connect cycles before the LITE/SLITE classification system was implemented. The underlying signal was real: your Connect document didn't reflect what the manager expected. The terminology has been largely replaced by the formal descriptor system since 2023.

One more structural change worth knowing: pre-PIP communication requirements were removed prior to Amy Coleman's April 2025 announcement. A manager can now initiate a formal PIP without any prior documented warning conversation. Per verified Microsoft engineers on Team Blind: "Around 4–5 months back, guardrails around the process of putting someone on PIP were removed, meaning a manager can put someone on 0 rewards (instant let go) or 60 (PIP or GVSA) without prior communication. This was a deliberate change."

You may not see a Microsoft PIP coming.

---

The 5-Day Choice: GVSA or Fight

At the moment the PIP is presented, you have five business days to make an irreversible decision.

Option A: Accept the GVSA. You receive approximately 16 weeks of base pay as a lump sum. Access ends within the agreed timeframe. A two-year ban on rehire at Microsoft applies. Unvested restricted stock units (RSUs) do not vest. The GVSA is a legal agreement that waives most claims against Microsoft. Read every clause and ideally consult an attorney before signing.

Option B: Decline the GVSA and attempt the PIP. You remain employed and have up to 90 days to meet the improvement criteria. If you pass, you keep your job. If you fail, you are terminated with no severance and the two-year rehire ban still applies. Once you decline the GVSA, it is gone.

The math here is worth sitting with. The GVSA front-loads the only meaningful financial exit. The alternative is a 90-day plan with pass rates the community consistently describes as low, and a failure outcome that carries no financial cushion. As one verified Microsoft engineer summarized on Team Blind: "You can come back from a PIP, but it is a hard road paved with zero rewards. Better to look for better comp elsewhere."

The GVSA is also structurally revealing. According to AP7am's reporting on the April 2025 process, the offer is presented at initiation and disappears if declined. That's only economically rational if Microsoft expects most employees in this situation will not pass the PIP. A company genuinely optimistic about improvement would offer GVSA at the end of a failed plan, not before the plan starts.

---

Is Yours a Genuine Improvement Plan or a Managed Exit?

The answer depends on org, manager, and whether the company is in a cost-cutting cycle. The community consensus on Team Blind leans strongly toward managed exit: "When an official PIP occurs, HR is brought in to build a case against the employee." But genuine improvement attempts do happen, and the signals that distinguish them are worth knowing.

Signs the process may be genuine:

• The milestones are specific and measurable: a defined project, a concrete deliverable, an objective date. Not "demonstrate improved ownership."
• Your manager continues substantive conversations about the actual work, not just running documentation check-ins
• The success bar is achievable given your role and the timeline
• Your org hasn't recently gone through headcount pressure, a reorg, or cost-cutting targets

Signs it's more likely a managed exit:

• Milestone criteria are evaluative and subjective, using language that can be found deficient regardless of actual output
• Your manager's communication has shifted to formal summaries and process documentation with minimal substantive engagement
• Work you were handling has been quietly redistributed to others
• The PIP arrived after a calibration that overruled signals your direct manager had given you pre-review
• A new manager was assigned recently
• A team reorg, headcount reduction, or division-wide cost-cutting cycle is underway

The "Good Attrition" metric is also relevant here. Microsoft tracks how many low performers managers exit. That creates structural incentive to set goals the employee cannot meet. Not because individual managers are malicious, but because that's where the incentive structure points.

---

How Your Org Changes the Picture

Not all PIP experiences at Microsoft are equivalent. The variation by division is significant enough to factor into how you read your situation.

Azure and Cloud

Generally cited as the most performance-meritocratic division. Engineers describe it as more standard compared to other orgs. Post-2024, security contributions became a mandatory component of rewards outcomes for all engineers (Azure included), so undocumented security work is a specific gap to know about.

Windows, Office, and Legacy Divisions

Historically, formal PIPs were rare here. The culture leaned toward quiet management-out processes rather than formal documentation. Under the 2025 policy with mandatory LITE quotas per team, these divisions are now being required to document and act on underperformance at a scale they haven't historically used. A PIP in one of these orgs now may reflect the new policy rather than a genuine long-term performance trend.

Gaming (Xbox, post-Activision)

The most turbulent division. Microsoft's Gaming org experienced four major layoff waves between 2024 and 2025, including the January 2024 Activision cuts (1,900 employees) and deeper Xbox cuts in mid-2025 including studio closures. The "performance" framing has been applied extensively in an environment many engineers describe as primarily cost-driven. One former Xbox engineer told The HR Digest directly: "They keep saying it's about 'performance,' but I was exceeding targets." If you're in Gaming, treat the performance framing with significant skepticism about whether it reflects your actual record or a headcount target.

---

Your First Two Weeks

The first two weeks are where most of your options exist. The clock and the decision structure are working against you after that.

Days 1–5: The GVSA Decision Window

1. Read the PIP document carefully. Identify every stated goal, metric, and timeline. Flag anything vague or subjective. Criteria without objective measurement are easier for a manager to find deficient regardless of your actual output.

2. Make the GVSA decision with full information. Factors that push toward accepting: strong external prospects, active cost-cutting in your org, GVSA timed suspiciously close to an RSU vesting cliff. Factors that push toward fighting: the milestones are specific and achievable, your manager has demonstrated genuine investment in your development, and you have no external prospects yet.

3. Consult an employment attorney before signing anything. Washington State, where most Microsoft engineering roles are based, has strong employee protections. A 30-minute consultation can identify whether the PIP timing carries legal significance, particularly if it followed protected activity: a discrimination complaint, medical leave, or whistleblowing. Many employment attorneys offer free initial consultations. The GVSA waives most claims against Microsoft. Don't sign without knowing what you're waiving.

4. Start the external job search immediately. Not after the five days. This week. The PIP period is runway, not a waiting room.

5. Don't sign the GVSA under pressure without reading it in full. If you need more time to consult counsel, request it. It may not be granted, but the ask is worth making.

Days 6–14: If You've Decided to Fight

6. Start a personal documentation log outside Microsoft systems. Personal email or personal device. Record every meeting, piece of feedback, and manager communication with exact dates, attendees, and language used. You are now building your own record in parallel to the one HR is building about you.

7. Request written clarification of every PIP goal. Push until you have specific, measurable criteria. "Improve team collaboration" is not a goal. "Deliver X feature with cross-team sign-off by Y date" is. Get the clarification in writing via email.

8. Pull together your prior Connects documents. Your self-assessments, peer Perspectives feedback, and any prior positive manager communication. If the PIP narrative contradicts your documented performance history, capture the inconsistency explicitly in your personal log.

9. Check your vesting timeline. A PIP initiated just before a vesting cliff can carry legal significance. An employment attorney can advise whether the timing matters in your situation.

10. Talk to trusted peers outside Microsoft channels. If others in your org are receiving similar treatment (especially after a manager change or during a cost-cutting period), documented patterns across employees strengthen any legal or HR challenge.

If you're on an H-1B visa (a US work authorization tied to your employer): Contact an immigration attorney within the first week regardless of which path you choose. Both the GVSA and PIP failure carry visa implications. Understanding your 60-day grace period, H-4 options if applicable, and O-1 pathways before making any decision is essential.

---

If You Decide to Fight It

Engineers who pass Microsoft PIPs share a few consistent approaches. It's a small group by community accounts, but the patterns are clear.

Meet the milestones exactly as written, not in spirit. If a goal specifies a design review with defined criteria by a specific date, hit every element and document it thoroughly. Evaluative milestones are easier to challenge if you document concrete actions mapped directly to the plan's exact language.

Don't resign. If you want out, negotiate or let the process complete. Resigning forfeits unemployment eligibility in most US states and eliminates leverage. If Microsoft wants to separate from you, require them to complete the formal process.

Watch for milestone drift. In documented cases, improvement targets became more demanding mid-PIP once it appeared the engineer might actually hit the original criteria. If that happens, you have both versions in writing. The original milestones and the revised ones. That documentation matters if you later challenge the process.

One harder truth from the community data: passing a Microsoft PIP is generally not a return to normal. Per Blind threads, post-PIP employees describe continued heightened scrutiny, no realistic promotion path in the near term, and frequent voluntary departure within a year or two. Passing buys you time. It doesn't always buy you a career at Microsoft.

---

If You're Leaving: What the Severance Looks Like

Path	Severance	Rehire ban	Notes
Accept GVSA	~16 weeks base pay	2 years	RSUs unvested; voluntary departure classification
Fight PIP, pass	None	None	Continued scrutiny; effectively no promotion path
Fight PIP, fail	None	2 years	Healthcare termination timing varies

Termination through PIP failure is involuntary. It qualifies for unemployment benefits in most US states. This step gets skipped often and shouldn't be.

Before the GVSA structure was formalized, Microsoft terminated approximately 2,000 employees for low performance in January 2025 with no severance, no formal PIP, effective immediately, per Allwork.space reporting. That wave is the floor case, showing what happens when Microsoft moves fast without the choice structure. The April 2025 GVSA formalization came partly in response to that approach.

For comparison: Amazon's Pivot program and Meta's formal PIP both run similar managed-exit structures. The GVSA is actually more generous than Meta's PIP exit terms (which offer no upfront severance) and comparable to Amazon's initial Pivot offer. That's worth recognizing even as you evaluate whether to take it.

For the broader picture of how PIPs work structurally across companies, What Is a PIP and What Does It Actually Mean? covers the foundation: the three types of PIPs, how to read the signals, and what engineers across companies typically do.

---

---

A Microsoft PIP is a fast-moving situation with a binary financial decision built into the first week. Whether you're evaluating the GVSA, building your case to fight, or using the 90-day window to search aggressively, having your contributions documented clearly matters. CareerClimb logs your wins, tracks your evidence, and builds the record that supports you through whatever comes next. Download CareerClimb and start building.