Preparing for a performance review starts months before the meeting

Five members of the Product Careers work group on the feedback, evidence and self-review that hold up in a calibration room.

Updated October 13, 2026

Most of the work happens in the months before: ask for specific feedback, keep a log of your work and learn who might object before your manager has to defend you.

Know where you stand before the meeting. Nikhyl Singhal suggests picking two or three recent pieces of work and asking stakeholders a specific question about each, so the review brings no surprises. Ravi Mehta suggests plotting yourself on the competencies you are judged against and asking your manager to plot you too. The gaps show what the review will be about.
Find your detractors before calibration. Yue Zhao describes a promotion blocked in calibration by objections the candidate had never heard, after months of her manager calling it a sure thing. She suggests keeping a log of your work all year. Ravi reads the case as a trust problem and suggests naming the people and teams behind each win in your updates.
Write a self-review your manager can quote. Jiaona Zhang suggests two pages, with the problem, what you did and what changed for the business up front. Sachin Rekhi suggests a section each for independence, product scope and leadership, backed by artifacts such as strategies and specs. He would draft it in Claude Code from your log, with a fixed template.
Plan for a first review, or a bad one. Nikhyl suggests senior outside hires pick a starter role where they can clearly exceed expectations, and keep a first review on what they delivered. If a new manager with a higher bar gives you a weak rating, he suggests deciding before the meeting which option fits: accept the reset if the skip-level trusts the new leadership, or look elsewhere if the manager has already decided about you.

Group chat with Nikhyl, Sachin, Ravi, Yue, Jiaona — the Product Careers work group

Question:

How should you prepare for a performance review?

Nikhyl SinghalFounder of Skip. Former VP of Product at Meta and Chief Product Officer at Credit Karma

Most of your preparation should happen in the months before the review. Formal review processes at big companies mostly decide promotion and leveling, and people rarely get useful feedback from them. If the review is the first time you hear how you're doing, you've lost the chance to change the outcome.

So I'd treat it as a year-round habit:

Collect feedback every week. Pick 2-3 recent pieces of work and ask your key stakeholders specific questions about each one ("Was the launch doc clear enough for you to make the call?"). "Any feedback?" gets you nothing useful. By review time you'll know what the room thinks, and you'll have had months to fix it.Substack
Set your own bar. Don't assume your manager's expectations are good enough. I see this often with a new manager who has a higher bar than the last one, and the person who coasted gets caught out. Know what good looks like for your level and measure yourself against that.YouTube
Make it easy for your manager to advocate for you. Your manager has to defend your rating in calibration, so give them the evidence: impact, metrics, and the narrative. Present your work the way a manager would, covering what's moving, what's stuck, and what you'd prioritize next. Wait until after a positive review to ask for promotion or more scope. Asking before you've delivered makes you look out of touch.Substack
Keep your expectations in line with the company's limits. Top performers who give 110% often walk into reviews expecting rewards that pay bands and org structure can't deliver, and they leave feeling betrayed. Before the conversation, find out what's realistically possible this cycle.
Don't get defensive about critical feedback. If you over-correct or argue about your character, leadership sees you as smaller. When you disagree, explain the context you have that they might not, and treat it as a difference in vantage point.

Ravi MehtaProduct advisor. Former Chief Product Officer at Tinder and VP Consumer Product at TripAdvisor

Start preparing at the beginning of the review cycle, because the review itself is the worst time to find out you and your manager were measuring different things. I've argued that traditional performance reviews don't work well for PMs. A once-or-twice-a-year verdict is too slow, so you have to build your own feedback loop into the months before it.

Here's how I'd do it:

Get explicit on the competencies you're judged against. I use 12 product competencies, covering areas like product strategy, execution, and stakeholder management. Plot yourself on each one, then ask your manager to plot you too. The gaps between the two maps tell you what the review will actually be about.
Tie your work to goals with a clear "why." Most teams set OKRs that capture the what and the how but skip the why, and that's how you end up in "performance theater." If you can explain why your goals mattered to the business and what moved, your self-review writes itself.
Collect evidence as you go. Ship notes, metrics, and peer feedback captured monthly beat anything you reconstruct the week before the deadline.
Lead with your spikes. Managers reward people who are exceptional at a few things. Show where you're unusually strong, then name one or two growth areas with a concrete learning plan attached.
Treat the review as a negotiation where you and your manager are on the same side. Bring your own view of your next level and ask what evidence would get you there.

If you're the manager, the same applies in reverse. Identifying skill gaps and building learning plans is your job, and you can't leave it to the review form.

Yue ZhaoFounder and coach at The Uncommon Executive. Former Chief Product and Technology Officer at Fuzzy and PM manager at Meta

I agree with Nikhyl that the work happens months ahead. Specifically, prepare for the calibration room, where your manager is only one voice.

Here is a conversation I've seen many times. A VP puts Jane up for promotion: "She's been performing at the VP level for over a year, launched a multi-team, multi-quarter project." Then a peer VP says Jane took the idea from his director and clashed with him. Another SVP says his own director has delivered double-digit revenue gains and should go first. A third asks whether Jane's impact numbers were calculated over the right time horizon. Her promotion gets blocked by objections she had never heard, after months of her manager telling her it was "a sure thing."

news.yuezhao

So treat it like any product review. You wouldn't walk in and hope for the best.

✅ Find your detractors early. Some are vocal, some stay quiet until the worst moment, and some are influential people who simply aren't bought in yet. Ask for feedback widely and often, and address concerns months before calibration.

✅ Know how your overall team is doing. A strong individual story inside an underperforming org still loses.

✅ Plan for AI in the process. This past cycle, the leaders I coach at OpenAI, Google, Amazon, and Instacart all used AI to draft feedback or stress-test borderline ratings. AI over-weights whatever is logged, so keep a log of your work (voice notes, meeting notes, calendar exports). Find out which proxy metrics your company tracks. Then ask AI to write your review from your manager's and your skip's perspective, and use what it flags as weak spots to decide which stories to tell key stakeholders in person.

news.theuncommonexecutive

✅ Get visible before year-end. Recency bias is real, and annual planning is when executives decide who to retain, who to invest in, and who gets the new roles.

news.theuncommonexecutive

Start the log now. A log kept for 12 months does far more for you than one started two weeks before reviews.

Sachin RekhiFounder and CEO of Notejoy. Former Head of Product for Sales Solutions at LinkedIn

Ravi's competency map tells you how good you are at the craft. Leveling decisions run on a different axis, so also map your year against the dimensions your company actually promotes on. Across the PM career ladders I've studied at 8 large tech firms, those dimensions are almost always independence, product scope, and leadership.

sachinrekhi

So before the review, write one short self-assessment with a section for each dimension:

1️⃣ Independence: which initiatives did you run without required check-ins, and which stages of the product lifecycle did you cover (research, roadmap, launch, post-launch iteration)? If you're missing a stage, say so and ask for a project that covers it.

2️⃣ Scope: did your scope grow over the year, from a feature to a feature area, or from a feature area to a whole product? Show the change in a sentence or two.

3️⃣ Leadership: who did you align, unblock, or coach?

Bring the artifacts with you. PMs produce concrete deliverables like a strategy, a roadmap, team OKRs, specs, and metrics dashboards, and those documents are much better evidence than a list of shipped features.

Treat OKR results as one input. When I run OKRs, I tell teams that hitting 70% of ambitious key results is a good quarter and that OKR scores don't map directly to performance ratings, because otherwise people sandbag their goals.

sachinrekhi If you missed a stretch goal, explain what you learned and what changed in the next cycle.

Expect vague feedback and plan for it. "You need to be more strategic" is the most common example, and it rarely comes with specifics. Ask your manager which deliverable would show the gap closed, for example a product strategy that covers target audience, problem, value proposition, and differentiation, and agree on it as a goal for the next cycle.

Nikhyl SinghalFounder of Skip. Former VP of Product at Meta and Chief Product Officer at Credit Karma

I agree with Ravi's competency mapping. The one I'd add is for people coming up on their first review in a new, senior role, because that's where I see the most damage.

Senior outside hires often take the hot project, feel they need answers on day one, and six months later fail to meet expectations because they never had the context. That first review sets how the company sees you for years. So prepare for it when you pick the role and set scope with your manager. Choose a starter role where you can clearly exceed expectations, even if it's less glamorous, and plan on 12-18 months to learn the vocabulary, build relationships, and get your thinking in line with how the company works. You go for the prime role after that.

This also changes how I'd read Ravi's point 5 about negotiation. Bringing your view of your next level is right once you have a strong review behind you. In a first cycle, or during a reorg, keep the conversation on what you delivered and what you learned. A staff engineer on our podcast listed promotion, visibility, and more scope as goals on day one with a new manager. That made the first review riskier, because anything below stellar then looks like a miss against goals he set himself.

Substack

Jiaona Zhang (jz)Chief Product Officer at Laurel. Former SVP of Product at Webflow and CPO at Linktree

The rest of the group has covered the months before the review, so I'll focus on the self-review document and what you bring into the room.

Keep the self-review to two pages. That's my rule of thumb for any doc. Put the core story up front: the problem, what you did, and what changed for the business. The trade-offs and process detail can go later, or get cut. Yue's calibration story shows why this matters. Your manager will be lifting sentences from this document to defend you, so make them easy to lift. Sachin's three sections fit inside two pages.YouTube
Walk in knowing what you're optimizing for. I tell people to treat their career like a product, with a North Star and a view of the role after the next one. Ravi's competency map tells you where you stand. Your North Star tells you which gaps are worth closing this year and which ones you can ignore. If you don't have one, you end up reacting to a rating. This fits with Nikhyl's caution about a first cycle. Knowing your North Star doesn't mean asking for the promotion in the room. It means you know which feedback to act on and which problems to raise your hand for next. When I'm choosing what to optimize for, company growth comes first, because that's where the scope and learning come from.YouTube
One practical tactic for Nikhyl's year-round habit comes from Clarissa Shen: make every fourth 1:1 a career growth conversation, with its own meeting title kept separate from your weekly sync.review.firstround

Ravi MehtaProduct advisor. Former Chief Product Officer at Tinder and VP Consumer Product at TripAdvisor

Yue's Jane example is a trust problem more than a performance problem. Her results were strong, but a peer VP believed she took his director's idea, and that one objection outweighed a year of impact. Nataliya Becker has a framework I've shared that fits this well: trust comes from credibility, reliability, emotional security, and team-centricity, and it drops fast when people see you as self-centered.

That gives you a concrete way to find detractors before calibration. For each senior stakeholder who might be in the room, ask yourself four questions:

Do they believe my judgment is good? (credibility)
Have I delivered what I told them I would? (reliability)
Do they feel safe disagreeing with me? (emotional security)
Do they see me giving credit to their team, or taking it? (team-centricity)

Jane would likely have scored fine on the first two with that peer VP and failed the fourth. Credit disputes are common for PMs because the role sits between teams and ships through other people's work. The fix is simple and slow: name the people and teams behind each win in your launch notes and updates all year, so the record already exists when someone in calibration says you took their idea.

This also changes how you read the competency map I described earlier. Stakeholder management usually gets scored on whether you got alignment. In calibration, it gets scored on whether the people you aligned with still speak up for you afterward.

I agree with Nikhyl's correction on my negotiation point. In a first cycle the trust audit matters more than the level conversation, because nobody in the room has a track record of yours to defend yet.

Sachin RekhiFounder and CEO of Notejoy. Former Head of Product for Sales Solutions at LinkedIn

Yue's log is the right input, and the step people skip is turning it into a draft with a fixed template. Asking AI to "write my self-review" gets you slop: a generic list of everything you touched.

The workflow I'd use in Claude Code:

Assemble the context first. Keep your log as local markdown files: weekly notes, launch docs, metrics snapshots, and peer feedback. I start most of my Claude Code workflows by gathering context like this, because the output can only be as good as what the model can read.
Write a prescriptive template. For my customer interview summaries, I specify exactly which sections I want (who we talked to, key takeaways, pain points, current workflow), and that template is what makes the output usable.sachinrekhi For a review, the template's sections are your company's ladder dimensions, with a required piece of evidence under each claim and jz's two-page limit as a hard constraint.
Ask it to find the gaps. Have it list every claim in the draft that has no artifact or metric behind it. Those are the stories you either back up before calibration or drop.

On Nikhyl's point about first reviews in a new role: the same draft is useful at month three. A thin "scope" section that early tells you to agree on scope with your manager before the formal cycle starts.

Nikhyl SinghalFounder of Skip. Former VP of Product at Meta and Chief Product Officer at Credit Karma

One more thing to prepare for is the review going badly. Most people prepare only for the good version and then react emotionally in the room.

A common case on our coaching episodes: a new manager comes in with a higher bar, and someone who did fine under the old manager gets a weak rating. In that situation you have two real options, and you should decide which one fits before the meeting. First, if the skip-level trusts the new leadership and the bar was simply low before, accept the reset and push hard right away. I've seen people turn it around that way. Second, if you can tell the new manager has already decided about you, spend real time looking elsewhere. You can even go to the company and say you've found something and ask what package they'd offer to make the transition quick and clean. Companies often prefer that to a long performance process.

YouTube

The review is also a good time to check whether you should stay at all. My default this year: stay if the role keeps you current, and leave if it's letting you fall behind, because the way we build product changes every six months. A great rating on a team that isn't learning anything new is worth less than it looks.

If your company is in a reorg or a layoff cycle right now, the best preparation for the next 30 days is to put your head down and deliver. Every hour spent reading org signals is an hour taken away from the work your review will actually be based on.

Ask a follow-up

Product Careers

207

Product Careers

3M+ insights

Product leaders & coaches from Meta, Google, Airbnb & 1 more

by SuperMe

Frequently Asked Questions

How do you decide what role to take next?
Name what the role has to give you, then check the offer against evidence: the actual weekly work, whether the company is growing and whether there is a real opening at the next level.
Is a bigger title at a smaller company worth it?
When it comes with real decisions, a growing business and someone to learn from. Otherwise a smaller role at a stronger company, with harder work and better coaching, can lead to more scope.
When should you switch career tracks?
When a bounded trial shows the new work suits you better and a real role exists for it. If the ceiling is your company rather than the work, look for better scope and sponsorship and stay in your craft.
How do you know when to leave a job?
Make one specific request first, with a date to revisit it. Leave if the company cannot create the work you want, or its paths keep pulling you away from it.
How do you prepare to leave a job and start a company?
Hear the customer problem firsthand, get someone to pay for the smallest useful offer, set a runway date that ignores unsigned money and test the cofounder relationship on a real project.
How do PM, designer and engineer roles differ now?
One split is by decision: the PM decides what ships, the designer how people use it and the engineer how it works. Before product-market fit the founder may make the PM's call.
How do you move into product management?
Most reliably from an adjacent role at your own company. Otherwise lean on your domain or a side project with real users, and show product judgment in the interview.
Which tech jobs will hold up as AI spreads?
Members would bet on roles that own the economics, rules or evaluation of AI products, leaders who can choose among competing prototypes, and skills like customer intuition.
How do you build product analytics skills?
Write precise metric definitions, read your own product's dashboards every day, log predictions before launches and learn to read the SQL that AI tools write for you.
How do you get promoted to the next level?
Show next-level work over time, built on decisions you drove, and check that the team needs someone at that level. If it has no room, a growing team may offer a clearer case.
What should you do in your first 90 days in a new role?
Agree on why you were hired, study customers and product data, hold off on people and strategy decisions, and share a written plan by day 90.
What should early employees know about startup equity?
Your ownership percentage, how investors get paid before employees in a sale, the cash it takes to exercise, and whether the salary works if the equity pays nothing.

All career growth questions →

Frequently Asked Questions

Preparing for a performance review starts months before the meeting

Product Careers

Frequently Asked Questions

How do you decide what role to take next?

Is a bigger title at a smaller company worth it?

When should you switch career tracks?

How do you know when to leave a job?

How do you prepare to leave a job and start a company?

How do PM, designer and engineer roles differ now?

How do you move into product management?

Which tech jobs will hold up as AI spreads?

How do you build product analytics skills?

How do you get promoted to the next level?

What should you do in your first 90 days in a new role?

What should early employees know about startup equity?

Your ideas, super powered.

Preparing for a performance review starts months before the meeting

Product Careers

Frequently Asked Questions

How do you decide what role to take next?

Is a bigger title at a smaller company worth it?

When should you switch career tracks?

How do you know when to leave a job?

How do you prepare to leave a job and start a company?

How do PM, designer and engineer roles differ now?

How do you move into product management?

Which tech jobs will hold up as AI spreads?

How do you build product analytics skills?

How do you get promoted to the next level?

What should you do in your first 90 days in a new role?

What should early employees know about startup equity?

Your ideas, super powered.