A first-time manager performance review template at Amazon should judge evidence, not sentiment.
First-Time Manager Performance Review Template for Amazon Teams
TL;DR
A first-time manager performance review template at Amazon should judge evidence, not sentiment.
The template has to force a manager to state outcomes, scope, tradeoffs, and the Leadership Principles that actually showed up in the work.
If the review cannot survive a calibration room where two managers disagree, it is too soft to use.
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 has 4 to 8 direct reports, a 30- to 60-day draft window before reviews are due, and a mandate to sound decisive without pretending to know everything.
It is also for skip-level leaders who need one template that works across AWS, retail, and operations without turning into generic praise.
Use it when you need a review packet that can be read in 5 minutes, defended in a 15-minute conversation, and still hold up when the room gets skeptical.
What should a first-time manager performance review template measure at Amazon?
It should measure output, judgment, and repeatability. Anything else is decoration.
In a Q3 calibration I sat through on an operations team, the manager brought a polished paragraph about “strong collaboration.” The room ignored it. The discussion moved to whether the person found the root cause, owned the fix, and prevented the same defect from reappearing. That is the Amazon lens. Not a personality score, but a decision record.
The template should answer four questions in plain language: what changed, who owned it, what tradeoff was made, and what happened after the decision. Not a list of tasks, but a trail of outcomes. Amazon reviewers do not reward busy people. They reward people who move the system and can explain why the system moved.
The best template also separates performance from potential. That distinction matters more than most first-time managers think. A person can be reliable, pleasant, and still not be operating at the level the role demands. The problem is not that they are nice. The problem is that niceness does not close a business gap.
> 📖 Related: [](https://sirjohnnymai.com/blog/amazon-vs-apple-pm-role-comparison-2026)
What should the template actually contain?
It should be short, structured, and hard to game. Long reviews create noise. Good reviews create judgment.
Use five blocks. First, role and scope. State the level, team, review period, and the work area. Second, outcomes. Name 3 to 5 concrete examples with the business result attached. Third, Leadership Principles. Map each example to the principle it actually demonstrates, not the principle you wish it demonstrated. Fourth, growth gaps. State the one or two behaviors that limited the person. Fifth, recommendation. Say whether the person is meeting, exceeding, or below bar, and why.
A first-time manager should not write a biography. The template is not a memoir. It is an evidence container. In practice, the strongest reviews are usually the ones that can be scanned line by line by a director who has never met the employee and still know what happened. That is the bar. Not elegant prose, but defensible judgment.
One useful discipline is to write one sentence for scope, one sentence for impact, and one sentence for risk. That is enough to keep the review from drifting into vague praise. If a sentence cannot survive a skeptical follow-up question, it does not belong in the template.
How do I write the review so calibration does not flatten it?
Write it for calibration, not for self-comfort. That is the real game.
In a Q4 review meeting I watched a manager lose an entire case because the draft sounded like advocacy. Every sentence praised effort. None of them named the hard tradeoff. A senior leader asked one question: “What did this person actually decide under pressure?” The room went quiet. That silence was the verdict. Not because the person lacked value, but because the template hid the evidence.
Calibration is organizational psychology, not paperwork. The room is not trying to read your intentions. It is trying to reduce ambiguity across managers. That means the template should make disagreement easy. If there is a weakness, name it directly. If there is a strength, show the behavior that makes it real. If there is a mixed signal, say so. Hidden nuance does not help in calibration. Clear nuance does.
The best reviews include counterevidence. That sounds uncomfortable, and it should. If the employee was excellent on execution but thin on strategic framing, write both. Not a praise sheet, but a field report. Not an advocacy memo, but a record of tradeoffs. The manager who can write that way gets taken seriously. The manager who cannot gets treated as someone who is protecting feelings instead of making calls.
> 📖 Related: meta-vs-amazon-career-compare-2026
How do I distinguish high performance from nice behavior?
High performance at Amazon is not being easy to work with. It is changing outcomes without needing constant rescue.
A common mistake from first-time managers is to reward visible helpfulness. That is the wrong signal. Helpful people can still create drag if they do not own a result. In one debrief I heard a manager describe an engineer as “always available” and “great partner.” The skip-level response was blunt: “Did they ship the thing?” That was the right question. Not because collaboration does not matter, but because collaboration without closure is not performance.
The template should separate behavior into three bins: does the person generate value, does the person increase team capacity, and does the person improve decision quality. Those are not the same thing. Someone can be technically strong and still be a poor multiplier. Someone else can be less polished and still move the team forward because they unblock work, make escalations early, and close loops without drama.
This is where Amazon teams are unusually unforgiving. The organization respects rigor, but it does not confuse rigor with delay. It respects ownership, but it does not confuse ownership with hoarding. It respects disagreement, but it does not confuse disagreement with indecision. The problem is not that people care too much. The problem is that they often care about the wrong evidence.
How do I run the review conversation with a direct report?
Keep the conversation direct, short, and specific. A review meeting is not therapy and it is not a surprise party.
In a strong first-time manager conversation, the opening is the judgment, not the warm-up. Say where the person stands, then show the evidence, then name the gap. Do not bury the conclusion under five minutes of throat-clearing. In a one-on-one after calibration, I watched a manager spend 12 minutes explaining the score and 3 minutes asking for the employee’s view. That ratio was backwards. The employee left confused, which meant the template had failed its second job.
The conversation should follow the same structure as the document. Start with the bottom line. Walk through the two or three examples that matter most. Explain what is expected next. Then stop. If the person argues every line item, the manager is probably over-explaining. If the person agrees too quickly, the manager may have written something too soft to be believed.
The best managers do not make the review conversation pleasant. They make it legible. There is a difference. Pleasant conversations fade. Legible conversations change behavior. That is the point.
What does a strong first-time manager template look like in practice?
It looks like a decision memo, not a journal entry.
A practical template for Amazon teams can fit on one page if it is disciplined. Put the employee’s name, level, review period, manager, and team at the top. Then use three core sections: outcomes, principles, and recommendation. Under outcomes, list the specific work and its effect on the business. Under principles, name the exact behavior that proved the point. Under recommendation, state the bar judgment plainly.
If you want the template to work across a 30-day, 60-day, and 90-day manager cycle, keep the language stable and the evidence fresh. That matters because first-time managers often confuse change with clarity. The template does not need to change every quarter. The evidence does. The manager’s judgment should become sharper, not longer.
One more point. The template should not read like an HR artifact. HR artifacts are safe and forgettable. Strong templates are slightly uncomfortable because they force a real call. That is why they work.
Preparation Checklist
The template only works if the manager does the evidence work first.
- Pull 3 to 5 concrete examples from the review period before writing anything.
- For each example, write the business result, the decision made, and the behavior that made it happen.
- Map each example to one Leadership Principle, but only after the behavior is clear.
- Write one sentence on scope, one on outcome, and one on the growth gap.
- Read the draft as if you were a skeptical director in calibration and remove every vague adjective.
- Work through a structured preparation system (the PM Interview Playbook covers performance narratives and debrief-style evidence mapping with real examples).
- Draft the review conversation separately from the written review so the live discussion does not become a reading exercise.
Mistakes to Avoid
The worst mistakes are not formatting errors. They are judgment errors.
- BAD: “Strong communicator, great attitude, always helpful.”
GOOD: “Resolved the launch blocker by escalating on day 2, clarified ownership, and prevented the defect from repeating.”
The first version is a compliment. The second version is evidence.
- BAD: Writing to be liked by the employee.
GOOD: Writing to be calibrated by managers who were not in the room.
A review that protects feelings but fails the room is not a good review.
- BAD: Confusing potential with current performance.
GOOD: Separating results, learning speed, and promotion readiness.
A first-time manager who mixes those three usually overpromotes weak evidence or undercalls strong work.
FAQ
- How long should a first-time manager review template be?
One page is usually enough. If the review needs two pages, the manager probably has too many examples or not enough judgment. The goal is not volume. The goal is a document that a senior leader can read quickly and challenge cleanly.
- Should the template mention Leadership Principles by name?
Yes, but only after the behavior is described. Names without evidence are cheap. Evidence without names is still useful, but Amazon teams expect the manager to connect the work to the principle that actually shows up in it.
- Can the same template work for strong and weak performers?
Yes, and that is the point. The structure should stay the same while the judgment changes. Strong performers get a clear case for impact and stretch. Weak performers get a clear case for the gap. Different conclusions, same standard.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.