Template for First PIP Conversation as New Manager at Amazon

TL;DR

The first PIP conversation is a standards-setting event, not a rescue. If you are new in role, your job is to make the gap legible, tie it to Amazon’s Leadership Principles, and leave no ambiguity about what changes, by when, and what happens if nothing changes.

The problem is not that the conversation is hard. The problem is that most new managers dilute it until it sounds optional. At Amazon, that usually reads as weak judgment, not compassion.

Use a 30-day correction window, weekly check-ins, and a written recap within 48 hours. The employee should leave with one clear message: this is a formal performance reset, not a vague development chat.

Not sure what to bring up in your next 1:1? The Resume Starter Templates has 30+ high-signal questions organized by goal.

Who This Is For

This is for the new Amazon manager who inherited an underperformer, a messy paper trail, or both, and now has to say the quiet part out loud without losing authority. It matters most if you are an L5 or L6 manager with little room for performative softness, because the team will read your first hard conversation as a preview of your standards.

If your skip-level is asking for documentation, if HR has started circling, or if your own manager has said "we need to address this cleanly," this is your conversation. In practice, the first PIP conversation is never just about one employee. It is about whether you can enforce the bar without turning the room into a drama.

What is the first PIP conversation really for at Amazon?

It is for alignment, not surprise. In a calibration room, the strongest argument is never "they are trying hard"; it is "here are the dated misses, the impact, and the bar they failed to clear."

At Amazon, the conversation should sound like an ownership decision, not a personality diagnosis. The Leadership Principles matter here because they give you a shared vocabulary. Customer Obsession, Ownership, Dive Deep, Insist on the Highest Standards, Earn Trust, and Deliver Results are not slogans in this setting. They are the standard you are enforcing.

In a Q3 debrief I sat through, the hiring manager kept defending a candidate as "promising" until the committee forced the discussion back to evidence. The room changed the moment the conversation stopped being about potential and became about pattern. A first PIP conversation works the same way. Not a punishment, but a reset. Not a therapy session, but a decision meeting.

The counterintuitive part is this: employees usually do better with a hard truth than with a soft warning. Ambiguity is more corrosive than rejection. If you are fuzzy, the employee hears room to negotiate. If you are precise, they hear the real bar.

> 📖 Related: Amazon L6 PM RSU Vesting: Why Back-Loaded Schedules Hurt Your TC in Year 1

How do I open the conversation without sounding weak or cruel?

Open with the decision, the gap, and the timeline. Do not warm up for ten minutes and hope the message lands by accident.

The first line should be direct enough that nobody can mistake it for routine feedback. A usable opening is: "I want to be direct. Your performance is not meeting the standard for this role, and we are starting a formal improvement process." That sentence does three things at once. It states the status, it names the standard, and it removes the possibility of false interpretation.

A new manager often makes the same mistake: they try to protect the employee from discomfort and end up protecting the employee from clarity. The problem is not harshness, but vagueness. Not empathy, but evasiveness. Not honesty, but half-truths.

In the room, the employee will often look for a softer interpretation. They will ask whether this is "just feedback," whether "things are really that bad," or whether "there is still time to turn it around." Your answer should be calm and repetitive. The message is formal. The bar is real. The plan is specific.

The organizational psychology here is simple. People can absorb bad news. They struggle with ambiguous news because ambiguity leaves them in a permanent state of self-edited panic. Clear structure is less humiliating than unclear concern.

What evidence should you bring into the room?

Bring dated facts, not impressions. If you cannot point to three concrete examples, you are not ready to hold the conversation yet.

In the best Amazon-style reviews, the manager walks in with a short packet: three misses, the expected behavior, the business impact, and the support that was already offered. That is enough. You do not need a 40-page dossier. You do need a pattern that survives interruption.

A good evidence set usually includes missed deadlines, incorrect deliverables, broken follow-through, customer impact, or repeated failure against a clear operating standard. If the issue is communication, show the messages. If it is execution, show the dates. If it is judgment, show the decisions and the downstream cost.

The mistake new managers make is treating evidence like a courtroom performance. It is not. It is a stabilizer. Not "I feel they are inconsistent," but "on April 4, April 12, and April 19, the same commitment was missed." Not "they seem disengaged," but "the deliverable was late twice and the follow-up was missing once the decision changed."

That distinction matters because memory is political. Once a difficult employee hears a vague accusation, they will fill the gap with excuses, grievances, and selective recall. Dated evidence closes that loophole. It also protects you when the conversation is later reviewed by your manager, HR, or a skip-level leader.

> 📖 Related: amazon-pm-vs-swe-salary

What does a real first PIP template look like?

It is a short structure with a fixed timeline, not a generic coaching outline. If your first PIP conversation has no date, no target, and no consequence, it is not a PIP conversation yet.

Use this shape:

  • State the decision.
  • Name the role standard.
  • Give three concrete examples.
  • Explain the business impact.
  • Set the correction window, usually 30 days.
  • Define weekly check-ins.
  • State the support you will provide.
  • Close with the next review date and the consequence if the bar is not met.

A manager who knows what they are doing does not ramble here. They keep the plan bounded. Thirty days is a credible correction window for many behavior and execution issues. Forty-five days can be reasonable if the work is process-heavy. Sixty days is already generous and should not become a way to avoid making a decision.

The key is not the number itself. The key is that the number means something. A deadline without a decision path is just calendar decoration. The employee should know whether the goal is to recover, to exit, or to prove the issue is actually a measurement problem.

A practical template sounds like this: "For the next 30 days, we will review these deliverables every week, and success means these specific outcomes are consistently met. If the pattern does not change, we will move to the next stage." That is not cruelty. That is managerial competence.

The insight many new managers miss is that PIP structure protects both sides. It protects the employee from moving goalposts. It protects the manager from drifting into performative coaching. It also keeps the organization from pretending that ambiguity is a management skill.

How do Amazon Leadership Principles change the conversation?

They make the conversation objective, which is exactly why Amazon uses them. The principles are not there to decorate the meeting. They are there to keep the feedback from becoming personal.

If the issue is missed commitments, tie it to Deliver Results and Ownership. If the issue is weak analysis, tie it to Dive Deep and Are Right, A Lot. If the issue is recurring defects, tie it to Insist on the Highest Standards. If the issue is poor communication, tie it to Earn Trust. That is the Amazon-specific move.

In a calibration meeting, I once watched a manager lose the room because they kept saying "the employee has good energy" while the actual problem was repeated missed deliverables. The senior leader cut through it with one question: "Which principle is this role failing against?" Once that question was asked, the discussion became honest very quickly.

That is the real organizational psychology at Amazon. The principles do not lower the bar. They make the bar discussable. Not "I don't like their style," but "this output is failing the standard." Not "they are not a culture fit," but "the work is not showing ownership, judgment, or follow-through."

For a new manager, this is the safest and strongest path. You are not inventing your own authority. You are enforcing the company’s own language. That is how you avoid sounding personal, arbitrary, or defensive.

What does the employee need to hear in the first 10 minutes?

They need to hear the truth, the bar, and the process. If they hear only the process, they will argue about paperwork. If they hear only the truth, they will panic. If they hear only the bar, they will leave without a map.

A strong first 10 minutes usually does four things. It names the performance gap. It explains the impact. It defines the timeline. It confirms the support. You do not need to debate every detail in that first pass. You do need to make the stakes unmistakable.

The best managers do not try to win the conversation. They try to make it executable. That means they stop talking once the message is clear, then give the employee room to respond. When the employee asks questions, answer them directly. When they push back, separate disagreement on facts from disagreement on the standard.

The instinct to over-explain is a trap. Not more words, but cleaner ones. Not more empathy theater, but more precision. Not more justification, but more structure.

If the employee is calm, good. If they are upset, still good. Emotional reaction is not the problem. Confusion is. A serious PIP conversation should not feel friendly. It should feel fair.

Preparation Checklist

Prepare the conversation like a formal decision, not like a coaching chat.

  • Write down three dated examples with the exact misses, the impact, and the standard that was missed.
  • Align with your manager and HR before the meeting so you are not freelancing the process.
  • Decide what support you can actually offer, such as clearer milestones, shadowing, or weekly review time.
  • Set a 30-day correction window and put the next review date on the calendar before the conversation starts.
  • Draft the written recap now, then send it within 48 hours after the meeting.
  • Rehearse the opening sentence until you can say it without hedging.
  • Work through a structured preparation system (the PM Interview Playbook covers the kind of debrief-style evidence framing and hard-feedback language that new managers usually get wrong on the first try).

Mistakes to Avoid

The fastest way to lose authority is to make the message feel optional.

  1. BAD: "I just wanted to talk about a few concerns." GOOD: "This is a formal performance conversation, and the gap is specific."
  2. BAD: "This is really just a development opportunity." GOOD: "This is a standards issue with a clear timeline and a clear consequence."
  3. BAD: "If you try harder, I think things will be fine." GOOD: "The standard is fixed, the support is defined, and we will review the result on the date we set."

The common thread is camouflage. New managers hide behind soft language because they want to preserve relationship equity. That usually backfires. The employee hears caution, not clarity. The team hears hesitation, not leadership. The business hears delay, not accountability.

A better rule is simple: if your wording would sound embarrassing in a calibration room, it is probably too soft for the employee conversation too. The room eventually hears everything.

FAQ

Is the first PIP conversation already a termination decision?

Usually not, but it is a decision point. If you do not believe recovery is possible, do not pretend the conversation is about development. That creates false hope and weakens your credibility. If recovery is possible, make the path explicit and bounded.

Should I say "PIP" in the first meeting?

Yes, if your process uses that term and the employee needs to understand the stakes. No, if you are using the word to sound official while avoiding the actual message. The label matters less than the clarity of the standard, the timeline, and the consequence.

What if the employee says the metrics are unfair?

Listen once, then return to the evidence. If the metric is broken, fix the metric. If the metric is valid, hold the bar. The mistake is turning every objection into a negotiation. Fairness is a real issue. It is not a reason to abandon accountability.

Sources used for factual grounding: Amazon Leadership Principles, Amazon.jobs Leadership Principles, Amazon manager training article

Related Reading