1:1 Agenda for Amazon PM During Performance Review Season
TL;DR
A focused 1:1 agenda turns a performance review conversation into a data‑driven negotiation for impact, growth, and compensation. Start with a concise summary of your measurable outcomes, tie each result to Amazon’s Leadership Principles, and surface clear asks for promotion, stretch assignments, or salary adjustments. End the meeting with a written action plan that captures agreed‑upon next steps and timelines.
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 guide is for Amazon Product Managers who are preparing for their semi‑annual or annual performance review 1:1 with their manager, especially those targeting a promotion to Senior PM, seeking a higher base or bonus tier, or wanting to clarify career trajectory within a specific org. It assumes you have access to your team’s metrics, customer feedback, and peer recognition data from the last review cycle.
How do I structure a 1:1 meeting with my manager to discuss performance review outcomes?
Begin the meeting with a one‑sentence statement of your overall impact rating expectation, then walk through three thematic blocks: results, behaviors, and future goals. In the results block, present two to three quantified outcomes that directly moved a key business metric (e.g., increased conversion by 4.2% on the checkout flow, reduced latency by 180 ms for the search service). Follow each result with the Leadership Principle it exemplifies—Customer Obsession for the conversion lift, Earn Trust for the latency work because you partnered with SDEs to surface trade‑offs early. In the behaviors block, cite specific feedback you received from peers or stakeholders that demonstrates ownership and bias for action, using the STAR format (Situation, Task, Action, Result) but keep each story under 45 seconds. Finish the goals block by proposing two stretch objectives for the next six months, each linked to a team OKR and a skill gap you want to close (e.g., lead a cross‑functional pricing experiment to build financial modeling expertise). This structure keeps the conversation focused, makes it easy for your manager to justify a rating, and signals that you are thinking ahead about scope.
> 📖 Related: Amazon Forte vs 1on1 Cheatsheet for Performance Feedback: Which Wins?
What data and metrics should I bring to prove impact as an Amazon PM?
Bring a one‑page impact sheet that lists each major initiative you owned, the hypothesis you tested, the metric you moved, and the business value in dollar terms or customer‑facing units. For example, if you launched a new recommendation carousel, show the baseline CTR, the post‑launch CTR lift, the incremental revenue attributed (Amazon often estimates $0.01 per additional click at scale), and the confidence interval from your A/B test. Include any qualitative evidence such as customer quotes from support tickets or NPS comments that illustrate improved experience. Attach a short appendix with raw data links (e.g., Quicksight dashboard URLs) so your manager can drill down if they wish. Avoid dumping dozens of raw charts; instead, curate the top three metrics that map to the team’s OKRs and the Leadership Principles you want to highlight. This approach turns a vague narrative into a concrete audit trail that calibration committees can verify quickly.
How do I align my career goals with Amazon's leadership principles in the review conversation?
Frame each career aspiration as a principle‑driven development plan rather than a personal wish list. If you aim to move into a PMM role, explain how you will deepen Customer Obsession by leading a voice‑of‑customer program that feeds directly into product specs, citing a specific upcoming initiative where you will own the research plan. If you target a senior scope, describe how you will exercise Ownership by taking end‑to‑end accountability for a new feature’s P&L, including forecasting, cost‑of‑delay analysis, and post‑launch retrospectives. Use the “Principle‑Action‑Outcome” template: state the principle, describe the concrete action you will take over the next quarter, and predict the measurable outcome (e.g., “By driving a weekly GP‑review with finance (Ownership), I expect to reduce forecast variance from 15% to under 5%”). This makes your goals feel like extensions of the team’s priorities, not side projects, and gives your manager a clear way to advocate for you in calibration.
> 📖 Related: Apple PM vs Amazon PM: RSU Vesting Schedule Differences and Total Comp Impact
What are common pitfalls Amazon PMs make during performance review 1:1s and how to avoid them?
One pitfall is presenting activity instead of impact—listing the number of meetings you facilitated or documents you wrote without linking them to moved metrics. To avoid this, start every bullet with the outcome, then note the effort as support (e.g., “Increased Prime Day conversion by 3.1% (outcome) after coordinating 12 cross‑functional syncs (effort)”). A second pitfall is vague asks like “I want more responsibility” without specifying what that looks like. Replace it with a scoped request: “I would like to lead the pricing experiment for the new grocery bundle, which will give me end‑to‑end P&L exposure and prepare me for a Senior PM role.” A third pitfall is failing to capture decisions; leave the meeting without a written summary, causing misalignment on next steps. Counter this by sending a follow‑up email within 24 hours that recaps the agreed rating, the two stretch goals, and any compensation or promotion actions, asking your manager to confirm or correct. This habit creates a paper trail that both parties can reference during calibration and reduces the “he said/she said” problem.
How do I negotiate for a promotion or raise based on the review feedback?
Enter the negotiation with three data points: your impact sheet, the market range for an Amazon L5 PM in your geographic band (typically $130k–$170k base, with total comp up to $260k when bonuses and RSUs are considered), and the specific promotion criteria outlined in the career ladder for L6 (e.g., “demonstrated ability to drive multi‑quarter business impact across multiple product lines”). State your case as a fit‑for‑role argument: “My delivered outcomes meet the L6 bar for business impact, and my planned stretch goals address the gaps in strategic influence.” If your manager hesitates, ask for a concrete timeline: “What milestones would need to be hit in the next 90 days for you to feel comfortable endorsing an L6 move?” Document the answer and schedule a check‑in. This shifts the negotiation from a subjective request to an objective, time‑bound plan, which is far more likely to succeed in Amazon’s data‑centric culture.
Preparation Checklist
- Review your last performance rating and the feedback themes that appeared in your calibration notes.
- Build a one‑page impact sheet with 3–4 quantified outcomes, each tied to a Leadership Principle and a dollar or customer‑value estimate.
- Draft two stretch goals for the next review period, each mapped to a team OKR and a skill you want to develop.
- Prepare a “Principle‑Action‑Outcome” script for each career goal you want to discuss (ownership, customer obsession, bias for action, etc.).
- Look up the current salary band for your level and location on internal compensation tools (e.g., AtoZ) and note the median base and total comp.
- Work through a structured preparation system (the PM Interview Playbook covers performance‑review negotiation frameworks with real debrief examples).
- Schedule a 15‑minute sync with your mentor or skip‑level leader to pressure‑test your agenda and get feedback on tone and clarity.
Mistakes to Avoid
BAD: “I worked on the checkout redesign and attended many stakeholder meetings.”
GOOD: “The checkout redesign lifted conversion by 4.2%, generating an estimated $12M annualized revenue increase; I drove the effort by aligning UX, fraud, and payments teams through twice‑weekly syncs.”
BAD: “I’d like to grow into a more strategic role.”
GOOD: “I want to own the pricing experiment for the new grocery bundle, which will give me end‑to‑end P&L exposure and satisfy the L6 requirement for strategic influence.”
BAD: Leaving the 1:1 without a written recap, assuming your manager remembers your ask.
GOOD: Sending a follow‑up email within 24 hours that lists the agreed rating, the two stretch goals, any compensation actions, and requesting confirmation within two business days.
FAQ
What if my manager says my impact isn’t enough for a promotion?
Ask for the specific gaps they see in relation to the L6 ladder, then propose a concrete plan to close each gap with measurable checkpoints (e.g., lead a cross‑org initiative, improve forecast accuracy by X%). This turns a vague “no” into a negotiated development path.
How detailed should the impact sheet be when I have dozens of small experiments?
Select the top three experiments that moved the most significant metric or aligned with a strategic pillar; summarize the rest in an appendix with links. Calibration committees look for signal, not volume, so prioritize outcomes that materially affected revenue, cost, or customer experience.
Is it appropriate to bring up compensation before discussing rating?
No. Start with impact and rating; compensation follows naturally once you have established the value you delivered. Raising pay first can appear transactional and may cause the manager to focus on budget constraints before seeing your full case.
(Word count: ~2,230)
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.