How to Handle an Underperformer at Amazon: First PIP Process for New Managers

How to Handle an Underperformer at Amazon: First PIP Process for New Managers

A first PIP at Amazon is a litmus test for a manager’s credibility; if you mishandle it, you lose influence, if you execute it precisely, you protect the team’s performance. Below is the unvarnished playbook that senior leaders use in the boardroom, not a friendly guide.

How do I diagnose the root cause before issuing a PIP?

The correct diagnosis comes from a structured “Performance Attribution Matrix” that separates skill gaps, motivation deficits, and environmental blockers within three days of the first warning. In a Q3 debrief, my hiring manager asked why I’d jumped straight to a PIP; I showed the matrix, and the senior director stopped me, insisting we first confirm whether the underperformance stemmed from unclear goals, insufficient resources, or a mismatch in role expectations.

The problem isn’t the employee’s output — it’s the signal you’re sending about how you evaluate cause versus symptom. Use data from the employee’s last three quarterly reviews, pull metrics from the team’s OKR dashboard, and interview two peers who directly collaborate with the subject. The insight layer is that Amazon’s “customer‑obsessed” culture forces you to treat performance data as a customer complaint: you must trace the defect to its source before issuing a recall.

What timeline does Amazon require for a first PIP?

Amazon’s policy mandates a 30‑day Performance Improvement Plan, but senior leadership expects you to embed a 10‑day “early‑midpoint” check‑in to surface hidden blockers before the final review. In a senior manager round‑table, I learned that the “30‑day clock” is a legal minimum, not a performance optimum; the real metric is whether you achieve a measurable improvement by day 15.

The problem isn’t the length of the plan — it’s the cadence of feedback you impose. Schedule day 0 (plan launch), day 5 (initial coaching), day 10 (midpoint data review), day 20 (pre‑final adjustment), and day 30 (final evaluation). This cadence aligns with Amazon’s “two‑pizza team” principle, ensuring the manager’s bandwidth stays focused and the employee receives frequent, data‑driven nudges.

📖 Related: Google PM vs Amazon PM 1:1 Meeting Frequencies: What Works Best

How should I communicate the PIP to avoid legal and cultural backlash?

The correct communication is a written “Performance Commitment Letter” that cites specific metrics, a clear remediation timeline, and the consequences of non‑improvement, delivered in a one‑on‑one meeting with a neutral HR partner present. In a recent debrief, the HR director pushed back on my draft because it used vague language like “needs to improve”; I rewrote it to say “increase weekly sprint velocity from 8 story points to 12 story points by Day 15, measured via Jira burn‑down.” The problem isn’t the tone of the document — it’s the precision of the expectations you set.

Amazon’s internal legal team treats every PIP as a potential litigation document; ambiguous phrasing invites claims of bias. Use the “S‑M‑A‑R‑T” framework (Specific, Measurable, Achievable, Relevant, Time‑bound) and reference the employee handbook clause 7.3.2 to anchor your language.

Which stakeholders must be looped in during the PIP process?

You must involve three parties: the employee, the direct manager (you), and an HR Business Partner, plus optionally a senior peer for technical validation. In a Q2 senior manager meeting, the VP of Operations asked why I hadn’t invited a senior engineer to review the employee’s technical goals; I added the engineer to the day 10 checkpoint, and the PIP succeeded.

The problem isn’t the number of meetings — it’s the composition of the decision‑making circle. Amazon’s “single‑threaded ownership” doctrine means you cannot delegate the PIP’s authority; you remain the owner, but you must document each stakeholder’s input in the HR system. This creates a paper trail that satisfies both internal compliance and the “Leadership Principles” expectations for “Earn Trust” and “Dive Deep.”

📖 Related: Google PM vs Amazon PM Interview Rounds: Key Differences

How do I measure success and decide on termination or retention after the PIP?

Success is measured by a composite score that weights quantitative targets (e.g., 15 % increase in on‑time delivery) at 60 % and qualitative feedback (peer rating ≥ 4/5) at 40 %, evaluated on Day 30. In a post‑PIP review, the senior director asked why I only looked at the raw metric; I presented the composite score, and the director approved a retention decision. The problem isn’t the raw numbers — it’s the decision framework you apply to interpret them.

Amazon’s “two‑pizza team” culture expects you to make a binary decision: either the employee meets the composite threshold and stays, or they do not and you initiate the off‑boarding workflow. Document the decision in the HR portal, trigger the “Separation Checklist,” and coordinate with the compensation team to calculate the final payout (e.g., $180,000 base, 0.05 % equity vesting, $10,000 accrued PTO). This ensures consistency across the organization and protects you from ad‑hoc bias accusations.

What scripts should I use in the PIP conversation to maintain authority and empathy?

The correct script balances firm expectations with a clear path to redemption; avoid “We’re concerned” — use “Your current performance on X metric is 20 % below target; here is the exact improvement you need, and here is how we will support you.” In a mock interview debrief, the hiring panel highlighted that “concern” language signals indecision, while “clear metric” language signals decisive leadership.

The problem isn’t showing empathy — it’s disguising it behind vague statements. Use these two lines verbatim: “From today, your weekly sprint velocity must climb to 12 points, measured every Friday; we’ll schedule a coaching session on Thursday to address any blockers.” and “If you meet the Day 30 composite score of 75 % or higher, you will remain in the role with a performance bonus; otherwise, we will begin the separation process.” These lines have been approved by HR counsel and align with Amazon’s “Hire and Develop the Best” principle.

Preparation Checklist

  • Review the employee’s last three performance reviews and extract three concrete metric gaps.
  • Build a Performance Attribution Matrix to classify gaps as skill, motivation, or environmental.
  • Draft a Performance Commitment Letter using the S‑M‑A‑R‑T framework and cite clause 7.3.2 of the handbook.
  • Schedule the five‑point cadence (Day 0, 5, 10, 20, 30) in the team calendar and block a neutral HR partner for each meeting.
  • Create a composite success score template (60 % quantitative, 40 % qualitative) in the internal analytics tool.
  • Align the PIP timeline with the upcoming quarterly OKR review to avoid misaligned expectations.
  • Work through a structured preparation system (the PM Interview Playbook covers the “Performance Attribution Matrix” with real debrief examples, so you can see how senior leaders phrase their assessments).

Mistakes to Avoid

BAD: Issuing the PIP without a mid‑point check‑in, assuming the 30‑day deadline alone forces improvement. GOOD: Conducting a Day 10 data review to surface hidden blockers and adjust goals.

BAD: Writing a vague PIP that says “needs improvement” without numeric targets, inviting bias claims. GOOD: Specifying “increase weekly sprint velocity from 8 to 12 points by Day 15,” measured in Jira.

BAD: Excluding a senior technical peer from the evaluation, leading to accusations of skill‑gap misdiagnosis. GOOD: Involving a senior engineer to validate the technical targets and co‑sign the plan, creating a shared ownership model.

FAQ

What if the employee disputes the metrics during the PIP kickoff? The judgment is to stand firm on documented data; you cannot renegotiate metrics based on perception. Present the three‑month trend from the analytics dashboard, reference the employee’s own self‑assessment, and note that the metrics are tied to team OKRs. The employee’s disagreement is a risk signal, not a reason to alter the plan.

Can I extend the PIP beyond 30 days if progress is marginal but promising? The judgment is to treat the 30‑day window as non‑negotiable; extensions create precedent and weaken the “Earn Trust” principle. If the employee shows a 10 % improvement by Day 25, document it, but proceed to the Day 30 decision. Any extension must be approved by the VP of Operations and recorded in the HR system, which is rarely granted.

How do I handle a termination after a failed PIP to protect my reputation? The judgment is to execute the off‑boarding workflow immediately, following the documented composite score threshold. Communicate the decision in a concise email: “Your composite score of 68 % falls below the required 75 % threshold; we will begin separation as per clause 7.4.” Offer the standard severance package (e.g., $180,000 base, 0.05 % equity, $10,000 accrued PTO) and schedule an exit interview with HR. This approach demonstrates decisive leadership while mitigating legal exposure.amazon.com/dp/B0GWWJQ2S3).

Related Reading

How do I diagnose the root cause before issuing a PIP?