First-Time Manager: How to Handle an Underperformer at Amazon Using the PIP Process

The PIP is not a documentation exercise. It is the most politically dangerous tool a first-time manager wields at Amazon, and most misuse it because they confuse process compliance with performance improvement.

I sat in a debrief once where a director-level hire was almost denied promotion to VP because she had initiated three PIPs in eighteen months and zero employees had improved. The hiring committee did not care that she had followed HR protocol exactly. They cared that she had failed to diagnose whether the problem was talent, fit, or her own management failure. That distinction is what this article addresses.

What Actually Triggers a PIP at Amazon vs. What Should?

A PIP should be the formalization of a decision already made, not a fishing expedition for whether someone belongs.

In my second year as a PM lead, I watched a new manager put a senior engineer on PIP because his sprint velocity had dropped 30% over two quarters. The documentation was flawless. The problem was that the engineer had quietly taken over on-call rotation for a teammate on medical leave, mentored two new hires, and rebuilt a failing CI pipeline that saved the team four hours weekly. The manager had measured output without understanding context. The PIP failed. The engineer left for Google within sixty days.

Amazon's leadership principle of "Insist on the Highest Standards" does not mean every gap deserves a PIP. The first counter-intuitive truth is this: the problem is rarely the underperformance itself.

The problem is the manager's diagnostic failure. A PIP is appropriate when three conditions converge: the gap is fundamental to the role, you have already provided coaching and clear feedback without improvement, and the employee has the capability to close the gap with structured support. Not "this person is frustrating," not "HR says I need documentation," not "my skip-level expects faster results."

In a Q3 debrief, the hiring manager pushed back because a candidate had described putting three people on PIP in fourteen months as evidence of "holding a high bar." The debrief went sideways when someone asked how many had succeeded. The answer was one. The committee read that as either poor hiring judgment or poor management, and the candidate was downleveled.

How Do You Write an Amazon PIP That Is Both Defensible and Fair?

A defensible PIP contains no surprises to the employee and no ambiguity to HR or legal.

The structure matters less than the specificity. I have seen PIPs with elegant SMART frameworks that were unactionable because the "measurable" column contained phrases like "improve code quality" without defining who evaluates, against what standard, by what date. I have also seen brutally simple documents that succeeded because they named the exact behavior, the exact gap, and the exact evidence that would constitute success or failure.

Here is the script I have used: "By [date], you will [specific action] as evidenced by [specific artifact or metric]. Success means [threshold]. Failure means [consequence]. We will review progress on [specific dates] with [specific reviewer]." The parenthetical peer aside: the PM Interview Playbook covers structured feedback frameworks with real debrief examples where this exact phrasing separated candidates who passed from those who were rejected for "vague communication."

The timeline at Amazon is typically thirty to ninety days. The first thirty days should contain weekly check-ins with documented feedback. The second thirty days allow for adjustment. The final thirty days are evaluation. Not "set and forget." Not daily micromanagement. A rhythm that signals seriousness without panic.

The second counter-intuitive truth: most PIPs fail because the manager writes them to protect against legal risk rather than to enable success. The document reads like a contract. The employee reads it as pre-termination paperwork. The psychological contract is broken before the process begins.

> đź“– Related: Amazon vs Apple PM Behavioral Interviews: STAR vs Secrecy Techniques for 2026

What Happens in the Weekly Check-Ins During an Amazon PIP?

Weekly check-ins are where PIPs are won or lost, and most first-time managers treat them as status updates rather than coaching interventions.

In a typical failed PIP I reviewed, the manager and employee met for thirty minutes weekly. The manager asked "how are things going," the employee said "fine," and both parties documented the conversation. After sixty days, the employee was surprised by the final evaluation. The manager was frustrated that "nothing had changed."

The structure that works: ten minutes of data review, fifteen minutes of obstacle diagnosis, five minutes of next-week commitment. The data review compares actual output against the PIP metrics with no editorial. The obstacle diagnosis asks "what specifically prevented success this week" and treats the answer as a hypothesis to test, not an excuse to accept or reject. The commitment is one behavioral change, not twelve.

I once coached a first-time manager whose employee consistently missed delivery dates. The PIP metric was "deliver 90% of committed stories on time over thirty days." Week one, the data showed two of three stories late. The obstacle diagnosis revealed the employee was waiting for design sign-off that arrived unpredictably. The commitment was not "try harder" but "schedule design review forty-eight hours before story start, and if sign-off is delayed, escalate to me within four hours." The employee succeeded. The PIP closed. The underlying skill—operational problem-solving—transferred to subsequent work.

The third counter-intuitive truth: the check-in is not about accountability. It is about calibration. The manager's job is to determine whether the gap is skill, will, or circumstance, and to adjust the plan accordingly. Not to be a taskmaster. Not to be a therapist. To be a diagnostician with a deadline.

How Do You Know When to Exit Someone vs. Invest More in a PIP?

The decision to exit should be made at the PIP midpoint with data, not at the endpoint with regret.

Amazon's culture rewards "bias for action," which sometimes translates to "keep people too long because firing is uncomfortable" or "fire too fast because the business needs the headcount." Neither serves the team or the individual. The correct midpoint evaluation asks three questions: has the employee demonstrated sustained behavioral change, has the output gap closed measurably, and has the team dynamic improved?

I witnessed a hiring committee debate a manager candidate who described extending a PIP twice because "the person was trying so hard." The committee's judgment was unanimous: emotional attachment masquerading as management. The employee was eventually terminated after eight months of documented struggle, having lost confidence, social capital, and months of job-search timing. Earlier, cleaner decisions serve everyone better.

The specific numbers that matter: if an employee has not shown measurable improvement against PIP metrics by day forty-five, the probability of ultimate success drops below 20% based on my observed cases. Not zero. Low enough that continuing requires explicit justification to yourself, your manager, and HR. If the gap is capability, more time rarely helps. If the gap is motivation, more time often confirms it. If the gap was circumstantial and now resolved, the PIP should close early with clear documentation of success.

The exit conversation itself follows this script: "We have reached the end of the PIP period. Based on [specific data], we have not seen the required improvement in [specific area]. Today we are moving to [specific next step, typically separation with package details]. I want to acknowledge [specific contribution the person made]." Do not negotiate in real-time. Do not express personal regret that invites debate. Do not delay past the decision date because "tomorrow is better."

> đź“– Related: comparison-of-tech-lead-roles-at-amazon-vs-google

Preparation Checklist

  • Diagnose before documenting: spend two weeks confirming the gap is real, not contextual, before initiating any formal process
  • Write the PIP backward from success: define what "fixed" looks like in observable terms, then construct the thirty-to-ninety-day path
  • Work through a structured preparation system (the PM Interview Playbook covers manager interview scenarios with real PIP debrief examples that distinguish "process follower" from "talent developer")
  • Schedule calendar-protected weekly check-ins with written pre-reads before each meeting
  • Brief your skip-level and HR partner simultaneously, not sequentially, to avoid conflicting guidance
  • Prepare the exit conversation before the midpoint evaluation so you are not improvising under pressure

Mistakes to Avoid

BAD: "I need to put you on a PIP to help you improve." GOOD: "I have documented a gap between your current output and the bar for this role. This PIP is the path to close it, with specific support from me."

The BAD version signals the PIP is optional or punitive. The GOOD version frames it as a structured final opportunity with mutual obligation.

BAD: Extending a PIP beyond ninety days because "progress is being made." GOOD: Closing the PIP at day sixty with success documentation if metrics are met, or moving to exit if they are not.

The BAD version destroys team morale and individual dignity through prolonged uncertainty. The GOOD version respects everyone's time.

BAD: Using PIP language in the first feedback conversation. GOOD: Using explicit "coaching" language for months, reserving PIP terminology for when formal process is actually initiated.

The BAD version creates premature documentation that can be used against the manager in arbitration. The GOOD version establishes a clear before-and-after that demonstrates good faith effort.

FAQ

What if my underperformer claims the PIP is unfair or retaliatory?

Document your prior coaching conversations with dates and specific examples. The antidote to retaliation claims is a contemporaneous paper trail of good-faith effort before any formal process. Most first-time managers fail here by giving verbal feedback without follow-up email confirmation. The employee's subjective experience matters less than your objective pattern of prior intervention.

How do I handle team morale when someone is on PIP?

Do not announce it. Do not hide it evasively. When asked directly, say "I am working with [name] on some specific development areas" and redirect to team priorities. The team already knows. Your job is not to manage their knowledge but to prevent the PIP from becoming a spectacle that distracts from delivery. The fastest morale recovery is a clean, fast resolution in either direction.

Should I ever PIP someone I just inherited on a new team?

Only if you have independent evidence of the gap. The first ninety days on a new team are for observation, not action on inherited performance issues. PIPing someone you have not managed through a full performance cycle signals either that you are performing someone else's unfinished work or that you are avoiding your own diagnostic responsibility. Neither reads as management strength to senior leadership.

---amazon.com/dp/B0GWWJQ2S3).

Related Reading

What Actually Triggers a PIP at Amazon vs. What Should?