This is not a performance review — it’s a diagnostic. Your first 1on1 with an underperforming direct report as an Amazon PM manager must establish psychological safety while mapping root causes, not symptoms. The goal isn’t to fix in one meeting, but to create alignment on data, define accountability, and signal support — with documented follow-up.
Template for Your First 1on1 with an Underperformer as an Amazon PM Manager
TL;DR
This is not a performance review — it’s a diagnostic. Your first 1on1 with an underperforming direct report as an Amazon PM manager must establish psychological safety while mapping root causes, not symptoms. The goal isn’t to fix in one meeting, but to create alignment on data, define accountability, and signal support — with documented follow-up.
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
You’re a newly promoted or recently hired Amazon Product Manager stepping into a leadership role with existing team members, and one or more are underperforming against bar-raiser standards. You’ve reviewed their deliverables, spoken to peers, and confirmed the gap — now you need to lead the conversation without triggering defensiveness or eroding trust. This is for PMs in Orgs like Alexa, AWS, or Retail where bar-raiser calibration is non-negotiable.
How do I structure the first 1on1 with an underperformer at Amazon?
Start with context-setting, not confrontation. Walk into the meeting with a clear timeline: 30 minutes total, 5 for rapport, 15 for data-based observation, 5 for their perspective, 5 for co-defined next steps. The structure isn’t about control — it’s about predictability. In a Q3 debrief last year, a hiring manager pushed back when a new PM ran a 60-minute open-ended session with no agenda. “You’re not giving clarity,” they said. “You’re creating anxiety.”
Not feedback, but discovery.
Not evaluation, but joint diagnosis.
Not urgency, but intentionality.
Amazon’s Leadership Principles (LPs) aren’t slogans — they’re diagnostic tools. Anchor your questions to specific LPs: Ownership if deadlines are missed, Dive Deep if analysis is shallow, Earn Trust if collaboration breaks down. One S-Team PM used Insist on the Highest Standards to frame a conversation with a PM who shipped a feature with known UX gaps. “It wasn’t about the feature,” they later told me. “It was about whether they knew it was below bar — and why they shipped it anyway.”
The real risk isn’t underperformance — it’s misattribution. In a People Review calibration, I saw a manager label a PM as “low drive” when the real issue was unclear requirements from upstream teams. The fix wasn’t coaching — it was unblocking. Your first meeting is a fact-finding mission. Assume positive intent until data disproves it.
> 📖 Related: meta-vs-amazon-career-compare-2026
What data should I present — and how?
Bring objective outputs, not opinions. That means PR/FAQ drafts with bar-raiser rejections, roadmap delays with owner attribution, peer feedback from at least two sources, and customer impact metrics (e.g., “CSAT dropped 12 points post-launch”). At Amazon, we don’t say “you’re not communicating well.” We say, “in the last three PR drafts, the ‘Why Now’ section was marked incomplete by bar-raisers.”
Not sentiment, but evidence.
Not generalization, but specificity.
Not tone, but traceability.
In a 2023 HC meeting for a Seattle-based team, a PM was flagged for “lack of ownership.” The manager brought one example: a delayed dependency where the PM waited 14 days for another team to respond — but no documentation of escalation. The committee rejected the case. “That’s not underperformance,” a bar-raiser said. “That’s unclear escalation paths.” The manager had to go back and pull meeting notes, email trails, Slack logs.
Present data in three layers:
- Output (e.g., missed launch date)
- Process (e.g., no risk flag raised in weekly sync)
- Impact (e.g., $2.8M ARR delayed)
Use the STAR-P format: Situation, Task, Action, Result — plus Pattern. One underperforming PM repeatedly missed bar-raiser feedback cycles. The pattern wasn’t effort — it was time allocation. They were spending 70% of their time in design reviews, not PR writing. The fix wasn’t discipline — it was workload rebalancing.
How do I avoid defensiveness when discussing performance gaps?
Ask for their story before stating yours. Begin with, “I want to understand your experience over the last quarter,” not “Here’s where you fell short.” In a debrief after a failed promotion packet, a manager who led with data saw the PM shut down. Another who started with, “What’s been your biggest challenge lately?” uncovered a reporting-line conflict that HR had missed.
Not correction, but curiosity.
Not judgment, but joint inquiry.
Not blame, but shared responsibility.
Amazon’s culture rewards self-critique — but only when genuine. A PM who says, “I should have escalated sooner,” is demonstrating Ownership. One who deflects with, “The team didn’t respond,” risks violating Earn Trust. Your job is to create space for the former, not provoke the latter.
Use silence. After you present data, say, “What’s your take on this?” Then wait. Eight seconds of silence will feel like an eternity — but it works. In a People Development session, a director told us, “The first person to speak loses the room.” Let them process. Most underperformers already know the gaps — they’re waiting to see if you do, and whether you’ll weaponize it.
Avoid “feedback sandwiches.” They don’t work at Amazon. LP-based calibration is too precise for sugarcoating. Instead, use contrast framing: “I’m not questioning your commitment. I am concerned about the PR cycle time — it’s at 18 days, twice the team average. Help me understand what’s blocking you.”
> 📖 Related: [](https://sirjohnnymai.com/blog/meta-vs-amazon-pm-role-comparison-2026)
What should I commit — and not commit — to during the meeting?
Commit to support, not solutions. Say, “I’ll help you get the resources you need,” not “I’ll fix this for you.” In a Q2 HC, a PM’s manager promised to take over a struggling initiative. The committee flagged it: “That’s not leadership — that’s rescue. You’ve just removed accountability.”
Not dependency, but enablement.
Not override, but scaffolding.
Not substitution, but reinforcement.
At Amazon, you are accountable for your team’s performance — but not responsible for doing their job. One L6 PM tried to “help” by rewriting a direct report’s PR/FAQ. The bar-raiser found out and rejected the packet. “The PM didn’t write it,” they said. “They can’t defend it.” Ownership can’t be delegated — or borrowed.
Set boundaries: no vague promises like “things will get better.” Instead, commit to frequency of check-ins (e.g., “We’ll meet weekly for 30 minutes”), access to mentors (e.g., “I’ll connect you with a senior PM in Comms”), and review cycles (e.g., “I’ll give you feedback on PR drafts within 48 hours”).
Do not promise outcomes. Never say, “If you do X, you’ll get promoted.” Amazon’s promotion process is committee-driven — managers don’t control outcomes. One manager in AWS did this, and when the package failed, the PM filed a formal complaint. The lesson: control inputs, not outputs.
How do I document and follow up after the 1on1?
Write a meeting summary within 24 hours — no exceptions. Subject line: “1on1 Follow-Up: [Name] – [Date] – Key Actions.” Include:
- 2–3 observed performance gaps (with data)
- Their perspective (verbatim quotes if possible)
- Agreed-upon next steps (with owners and dates)
- Support you’ll provide
Send it to them and your manager. Bcc HR if gaps are severe.
In a London-based team, a manager skipped documentation after a tense 1on1. Three weeks later, the PM claimed they’d never been told about performance issues. The manager had no paper trail. The case was dismissed — and the manager was counseled for poor people leadership.
Not memory, but record.
Not assumption, but alignment.
Not trust, but verification.
Follow up with biweekly check-ins for 60 days. Track progress against the same metrics used in the first meeting. If there’s no improvement, initiate a Performance Improvement Plan (PIP) — but only after this cycle. Amazon expects documented effort before escalation.
One L5 PM in Devices ran three follow-ups with a struggling report. Progress was incremental but visible. When the case went to HC, the committee approved retention — not because performance was fixed, but because the process was sound.
Preparation Checklist
- Gather at least three data points showing performance gaps (e.g., missed deadlines, peer feedback, customer impact)
- Map gaps to specific Amazon Leadership Principles with examples
- Draft a 30-minute agenda with time allocations for each segment
- Schedule the meeting with at least 48 hours’ notice — no surprises
- Work through a structured preparation system (the PM Interview Playbook covers Amazon 1on1 diagnostics with real HC debrief examples)
- Share the agenda with your manager for alignment before the meeting
- Prepare 3–5 open-ended questions to elicit root causes, not excuses
Mistakes to Avoid
BAD: Starting the meeting with, “We need to talk about your performance.”
This triggers threat response. The person spends the next 25 minutes managing fear, not listening.
GOOD: “I want to get a better sense of what’s working and what’s not from your side. Can you walk me through the last quarter?”
This opens space for disclosure — and often surfaces the same gaps you’ve observed.
BAD: Presenting feedback as final verdict: “The bar-raisers rejected your PR because it’s subpar.”
This removes agency. It implies the decision is fixed and blame is assigned.
GOOD: “The bar-raisers had concerns about the ‘Why Now’ section. What was your thinking there?”
This invites reflection and shows you’re separating person from work.
BAD: Ending without clear next steps or follow-up dates.
This turns the meeting into venting, not action.
GOOD: “Let’s meet again in 7 days. Before then, please send me a revised PR/FAQ outline with the ‘Why Now’ section. I’ll review within 48 hours.”
This sets rhythm and accountability.
FAQ
Should I involve HR before the first 1on1 with an underperformer?
Only if there’s a behavioral issue or past PIP history. For performance gaps, it’s your responsibility as manager to lead the conversation. Involving HR too early signals escalation, not support. One L6 in Seattle triggered an HR case for a late deliverable — the committee called it “over-escalation.” HR should be looped in after the first meeting, not before.
How soon should I have this conversation after noticing underperformance?
Within 10 business days of confirming the pattern. Delaying signals tolerance. At Amazon, speed of action is part of Bias for Action. I’ve seen managers wait 6 weeks for a “better time” — by then, the team had lost confidence. The 10-day rule forces discipline without rashness.
Can I use the same template for senior PMs (L6/L7) as for junior ones?
No. For senior PMs, shift from task-level gaps to strategic impact. Don’t focus on PR turnaround time — focus on market capture delay or team throughput. An L7 underperformer at AWS was missing delivery dates, but the real issue was failing to unblock dependencies. The template changes from “execution” to “multi-team leverage.” Senior roles are evaluated on scope, not speed.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.