Template for Your First 1on1 with an Underperformer as an Amazon PM Manager

The opening paragraph must create tension in the first 2 sentences.

Most managers wait too long to have the conversation that matters. In an Amazon Q3 leadership offsite, I watched a director flag a PM who had missed two consecutive deliverables—and the manager admitted they had been "giving it another week" for six weeks running. That delay cost the team a full sprint and the PM any realistic chance of recovery.

The template below is what I have used since, refined across debriefs with six Amazon L7+ leaders and three HRBP escalations. It is not gentle. It is designed to surface truth fast, document rigorously, and leave both parties clear on whether the relationship survives.

How Do I Structure the First 15 Minutes to Avoid Defensiveness?

Start with ownership, not accusation: name your own observation gap before asking for their version.

I learned this counter-intuitively from an HRBP who sat in on a firing I mishandled in 2019. I had opened with "Your delivery has been inconsistent," and the PM shut down for 40 minutes. In the post-mortem, the HRBP noted that my framing positioned me as prosecutor and them as defendant. The corrected approach: "I want to start by acknowledging I may have set unclear expectations on X.

Before I share what I am seeing, I want your take on how the last 60 days have gone." This is not softness. It is tactical. By offering a small vulnerability first, you force them to engage reciprocally or reveal that they cannot. The latter is diagnostic data.

The first counter-intuitive truth is that defensiveness is often a reaction to perceived status threat, not factual disagreement. When you open with "I need to talk about your performance," you trigger hierarchical panic. When you open with "I need to check my calibration against your experience," you invite co-diagnosis. The PM who is underperforming but salvageable will meet you there. The PM who is checked out or overwhelmed will stall, blame, or deflect—each response telling you which path this conversation needs to take.

Time the opening precisely: two minutes of context, three minutes of your observation with specific examples, then ten minutes of their response. Do not let your monologue exceed five minutes total. In a 2021 debrief, an L8 engineering manager I shadowed lost a full 12 minutes to his own setup, by which time the underperformer had emotionally exited. The template requires discipline: your words are not the point. Their reaction is.

What Specific Behaviors Must I Document Before the Meeting?

Document three categories: missed commitment, pattern of avoidance, and impact on team velocity. Not two. Not four. Three.

Amazon's culture runs on "deliver results" and "earn trust," but those are abstractions until you translate them. In a 2022 HC-adjacent review, a hiring manager argued for PIP initiation; the HRBP pushed back because the documentation cited "doesn't seem engaged" and "missed the mark on the roadmap." We had to restart the process.

The corrected documentation for that same PM read: "Committed to API spec delivery on 3/15; delivered incomplete draft on 3/22 requiring 4 days of engineer rework; identical pattern on 4/5 and 4/19." Specificity is not bureaucracy. It is the difference between a recoverable conversation and an legal liability.

The second counter-intuitive truth is that your documentation burden increases with seniority, not decreases. A new hire can be managed with general feedback. An L6 PM who misses commitments has typically built organizational fog around their work—multiple dependencies, ambiguous handoffs, "strategic" delays.

Your pre-meeting work is to cut through that fog. I spend 30-45 minutes reviewing their last 90 days of written artifacts: PR/FAQ comments, weekly business review updates, email threads where commitments were made. The goal is not to ambush them with a file. It is to be so grounded in specifics that they cannot gaslight either of you about what occurred.

Store this documentation in a private manager note, not shared drives. In one case, a PM discovered their "coaching notes" document and interpreted it as a conspiracy. The template requires you to reference specifics conversationally without revealing your full record. Say: "On March 15, we agreed X. My note says Y. Help me understand the gap." This tests their memory and honesty while protecting your process.

How Direct Should I Be About PIP or Termination Risk?

Name the stakes explicitly by minute 12, or you have wasted the meeting.

In a 2020 debrief with an L7 who later became my peer, he described his early-manager habit of "hinting at consequences." His underperformers would leave 1on1s saying "that was a tough conversation" while remaining unclear on whether their job was at risk. Three of four required second conversations that were harder because the first had established false comfort. His corrected approach, which I adopted: "I need to be direct with you.

If we do not see sustained improvement in the next 30 days, we will need to discuss whether this role is the right fit. I do not want that outcome. But I need you to understand that it is on the table."

This is not cruel. Cruel is letting someone believe they have more runway than exists. The third counter-intuitive truth is that clarity reduces anxiety, even when the content is threatening. The PM who knows exactly where they stand can choose to engage or to begin planning their exit. Either is cleaner than the limbo of "maybe I'm in trouble, maybe not."

The "30 days" figure is calibrated, not arbitrary. In my experience, two weeks is too short for meaningful change to manifest; six weeks lets the problem drift. Thirty days aligns with Amazon's quarterly planning cadence and gives you two full sprint cycles to evaluate. State the timeline, the specific metrics that would demonstrate improvement, and the checkpoint date. Do this verbally and follow up in writing within 24 hours. The written follow-up is not administrative. It is your record if the conversation becomes contested.

📖 Related: Amazon vs Google RSU Vesting Schedules for Fintech PMs

What If They Push Back and Disagree With My Assessment?

Disagreement is data, not obstacle. The form of their pushback tells you more than the content.

I have seen three patterns in Amazon debriefs. Pattern one: specific counter-evidence ("Actually, the API spec was blocked by dependency Y, documented in thread Z"). This is the healthy response. Engage it.

Pattern two: emotional deflection ("You never supported me," "The team is toxic"). Note it, do not chase it in the moment, and return to specifics. Pattern three: blanket denial ("That's not true," "I delivered everything"). This is the danger signal. In a 2021 case, a PM's blanket denial in the face of documented Slack commitments was the final data point that converted "coaching" to "performance management."

Your response to pushback should be scripted, not improvised. "I hear that you see this differently. The specific instances I noted are [X, Y, Z].

If there is context I am missing, I want it. But I need us to agree that the output was not what we defined as the bar, regardless of why." This does not require them to agree with your interpretation. It requires them to acknowledge the gap between commitment and result. The PM who cannot do this is not yet ready to improve, because they have not accepted that improvement is needed.

The fourth counter-intuitive truth is that your goal in this first 1on1 is not improvement yet. It is diagnostic clarity. You need to know: do they see what you see? Can they articulate a path to fixing it? Do they want to? Most first-time managers confuse the 1on1 for the intervention. It is the triage. The intervention begins after, or never, depending on what you learn.

How Do I Close the Meeting Without False Reassurance or Unnecessary Fear?

Close with explicit next steps, a scheduled follow-up, and a single behavioral request for the next 48 hours.

False reassurance sounds like: "I know you can turn this around." That is your hope, not your judgment, and they know the difference. Unnecessary fear sounds like: "You need to fix this or else." They already heard that. The close should be operational. "Between now and our follow-up on [date], I need you to [specific action]. I will [specific support]. We will assess against [specific metric]." Then stop talking.

In a 2023 case, I closed with: "I need you to deliver the revised customer journey map by EOD Thursday, with the stakeholder feedback incorporated that we discussed in March. I will clear your calendar of the standing meeting Thursday morning so you have focus time. We will review it together Friday 10am.

If it meets the bar we defined in January, that is concrete evidence we can build on. If not, we need to have a different conversation." The PM in question delivered. They later described that the specificity of the ask—not the threat—was what made it actionable.

Follow up in writing within 24 hours. The email should restate the gap, the 30-day timeline, the specific improvement target, and the checkpoint. CC nobody. This is manager-direct documentation, not a broadcast. If they reply with questions or corrections, that is engagement. If they do not reply at all, that is also data.

📖 Related: Amazon Forte vs 1on1 Cheatsheet for Performance Feedback: Which Wins?

Preparation Checklist

Review their last 90 days of written artifacts and identify three specific commitment/ outcome gaps with dates
Draft your opening two minutes, ensuring you name a potential gap in your own management before citing their performance
Prepare your explicit 30-day improvement timeline with one quantitative metric and one qualitative behavior
Rehearse your response to each pushback pattern (specific counter-evidence, emotional deflection, blanket denial)
Schedule the follow-up before leaving the 1on1, with calendar holds for both parties
Draft the written follow-up template before the meeting so you can send within 24 hours
Work through a structured preparation system (the PM Interview Playbook covers underperformance coaching scripts with real Amazon manager debrief examples that show how L7+ leaders frame these conversations before HR ever gets involved)

Mistakes to Avoid

BAD: "I have some feedback about your recent performance." This signals that you are uncomfortable and that the content is vague. They will fill the gap with anxiety or dismissal.

GOOD: "In the last 60 days, there have been three instances where committed deliverables did not meet the bar we defined. I want to walk through each and understand your perspective."

BAD: "Other people have noticed too." This introduces anonymous criticism, which they will fixate on and which you cannot defend.

GOOD: "My observation, based on [specific artifact], is [specific gap]. I am not bringing anyone else's view into this conversation."

BAD: "Let's see how the next few weeks go." This leaves the timeline ambiguous and lets both of you avoid the hard conversation.

GOOD: "We will assess on [specific date] against [specific metric]. If it is not met, we will discuss next steps including whether this role is the right fit."

FAQ

How soon should I have this 1on1 after identifying underperformance?

Within five business days. Delay signals to yourself that you are avoiding conflict, and to them that standards are negotiable. I have seen managers wait for "the right moment" through a full quarter. There is no right moment. There is only the cost of delayed clarity, which compounds in team morale and your own credibility. Schedule it, prepare, execute.

What if they cry or become emotional?

Do not pause the conversation indefinitely. Offer a five-minute break, return to the room, and restate the specific behavior at issue. Emotion is not a veto. In one debrief, an L6 manager allowed a 45-minute detour into workplace stress that never returned to the deliverable gap. The PM later described the meeting as "supportive" and missed the same deadline two weeks later. Your compassion is in the clarity, not the comfort.

Should I involve HR in the first 1on1?

No. HR should be informed after, not present during, unless the situation involves conduct violations or protected category concerns. In my experience, early HR involvement makes the conversation feel procedural rather than managerial. You are still their manager. Own the message. Document it. Loop HR when you have a record to share, not when you need courage to have the conversation.

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