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

TL;DR

Performance management at Amazon is a highly mechanized, metrics-driven resource allocation process rather than a rehabilitation program. For a first-time manager, delaying the Pivot or Performance Improvement Plan process to protect an employee's feelings is a career-limiting mistake that signals a lack of leadership maturity. Executing this process successfully requires absolute alignment with your HR business partner, objective telemetry of performance gaps, and an immediate shift toward team-wide capacity planning.

Who This Is For

This guide is written specifically for newly promoted L6 or L7 managers at Amazon who are facing their first underperforming direct report—typically an L5 or L6 Product Manager or Software Development Engineer earning between $160,000 and $245,000 base salary—and need to navigate the transition between Focus, Pivot, and PIP under the pressure of annual talent calibration and forced attrition targets.

What is the difference between Amazon Focus and Pivot?

Focus is an informal, undocumented tracking stage where you establish clear expectations, whereas Pivot is the formal, HR-governed choice point where the employee must either accept a severance package or enter a Performance Improvement Plan. The critical difference lies in HR visibility and legal framework. Focus is an internal team management tool used to determine if an employee can close performance gaps without formal corporate intervention. The objective of the Focus phase is not to rehabilitate the employee, but to gather legally and operationally defensible data.

During a Q3 talent calibration in a Seattle Day 1 tower, a senior director made it clear that a manager's biggest failure during Focus is treating it as a secret. If you do not explicitly tell your employee they are in Focus, you are wasting time.

Focus typically lasts 30 to 60 days. During this period, you must assign concrete, short-term tasks with binary outcomes. For example, instead of asking an L6 PM to improve their document writing, you must assign them to deliver a complete, review-ready PRFAQ for a specific feature by Friday at 5:00 PM.

If the employee fails to meet these binary targets, you transition them to Pivot. Pivot is a formal corporate gate managed by HR. Once an employee is placed in Pivot, they are presented with a choice.

They can either opt to leave Amazon immediately with a severance package—which typically consists of 10 to 12 weeks of base pay, equating to roughly $35,000 to $45,000 for an L6—or they can choose to fight the decision by entering a formal 30-day Performance Improvement Plan. The problem isn't your feedback — it's your judgment signal. If you hesitate to move an employee from Focus to Pivot when the data warrants it, your leadership team will interpret that hesitation as your own inability to raise the performance bar.

How does a manager initiate the Pivot process for an underperforming employee at Amazon?

Initiating the Pivot process requires you to submit a comprehensive documentation packet to your HR Business Partner showing sustained underperformance during the Focus phase with clear, objective data points. You cannot start Pivot based on intuition or qualitative feedback. HR will reject any request that lacks a detailed log of the employee's work products, specific instructions provided, and the exact ways those work products failed to meet the L6 or L7 role guidelines.

In a calibration meeting for an underperforming Software Development Engineer, the hiring manager tried to initiate Pivot by arguing that the engineer was too slow. The HR partner immediately blocked the request because the manager had not documented the sprint-by-sprint story point delivery or contrasted the engineer's output against the team average of 15 story points per sprint.

To avoid this roadblock, you must maintain a weekly performance log during the Focus phase. This log must detail the task assigned, the date assigned, the expected standard of completion, the actual outcome, and the date the feedback was delivered.

Your role as a manager is not to act as an empathetic coach during calibration, but to operate as an objective business owner. Once your HR Business Partner reviews the log and agrees that the performance gap is persistent, they will seek approval from your L7 or L8 Director.

Once approved, HR will register the Pivot in the internal management portal, and you will schedule the formal Pivot delivery meeting. This meeting is highly scripted and structured to minimize legal liability for the company while giving the employee a clear, binary choice.

What scripts should an Amazon manager use when delivering a Focus or Pivot decision?

Managers must use direct, neutral, and unambiguous language that connects performance directly to business impact and level-appropriate expectations. Avoid long-winded introductions, emotional preambles, or apologetic language. Apologizing during a performance delivery meeting signals that you do not support the decision or that the decision is arbitrary, both of which undermine your authority and expose the company to legal risk.

When placing an employee into the Focus phase, use this script:

I have completed your performance evaluation for the past quarter, and I am placing you on a structured performance plan called Focus, starting today. This decision


More PM Career Resources

Explore frameworks, salary data, and interview guides from a Silicon Valley Product Leader.

Visit sirjohnnymai.com →

FAQ

How many interview rounds should I expect?

Most tech companies run 4-6 PM interview rounds: phone screen, product design, behavioral, analytical, and leadership. Plan 4-6 weeks of preparation; experienced PMs can compress to 2-3 weeks.

Can I apply without PM experience?

Yes. Engineers, consultants, and operations leads frequently transition to PM roles. The key is demonstrating product thinking, cross-functional collaboration, and user empathy through your existing work.

What's the most effective preparation strategy?

Focus on three pillars: product design frameworks, analytical reasoning, and behavioral STAR responses. Mock interviews are the most underrated preparation method.