The most effective way to prep for a performance review is to write your accomplishments in STAR format — Situation, Task, Action, Result — before the conversation. Performance reviews reward people who do the prep work: most reviews are short conversations where your manager arrives with maybe three things they remember (usually from the last 60 days), and you arrive with whatever you can pull together in the hour before. The asymmetry is the problem, and STAR is the format that closes the gap. It forces every accomplishment into a structure your manager (and your skip-level, and HR comp committees, and future hiring managers) can read in 15 seconds and understand the scope.
What does the STAR structure look like?
STAR is a four-part shape for describing a single accomplishment: Situation, Task, Action, Result. Many people write two to four sentences per accomplishment in that order — one sentence on the business context, one on what your specific responsibility was within it, one or two on what you concretely did, and one on what changed because you did it. Kept to that length, each entry can be read in about fifteen seconds, which is roughly the attention any single item gets from a manager, a skip-level, or a compensation committee. The structure also does something useful under pressure: it separates what you did from what was happening around you, so the credit lands on the actions rather than on the circumstances. Most people end up with five to eight of these for a year, written before the conversation rather than during it. The shape people write to:
- Situation: What was the business context? (1 sentence)
- Task: What was your specific responsibility within it? (1 sentence)
- Action: What did you do — concretely, with the verbs? (1-2 sentences)
- Result: What changed because you did it? Quantify if possible. (1 sentence)
The Result line is where most people undersell themselves. "Improved performance" is invisible. "Reduced p95 latency from 800ms to 180ms across 4 endpoints, unblocking the mobile team's launch" is undeniable.
How do you prep for a review, step by step?
Prepping for a review is mostly gathering, filtering, and rehearsing, and it tends to go better spread across a couple of sittings than done in the hour before the meeting. Many people start by pulling the year's signals into one document — calendar, pinned messages, code and design history, the goal tracker, 1:1 notes, customer emails — and listing everything they actually did without filtering yet. From that list they keep the five to eight items that map to their level or role expectations, then write each one as a STAR entry, holding it to four or five lines. Quantifying the Result is its own pass, and where a number does not exist a credible qualifier can stand in its place. The last two steps are rehearsal — the three strongest stories, told out loud — and submitting the self-review early enough to set the frame. How people generally work through it:
1. Pull the year's signals into one document
A common first step is to block 2 hours and open: your calendar, Slack DMs starred or pinned, GitHub/PR history, design docs you authored, OKR/goal tracker, manager 1:1 notes, customer feedback emails, and your own brag doc if you have one. Many people list the 10-20 things they actually did and hold off on filtering yet.
2. Filter to the top 5-8 that map to your level/role expectations
For each accomplishment, it often helps to write a one-line gut-check: does this match a behavior or outcome listed in your career level rubric? Items that don't map to the rubric still count, but most people let the rubric-aligned items lead.
3. Write each as STAR
Keeping it tight tends to work best — many people fit each STAR in 4-5 lines max. If you need more, you may be blending two accomplishments.
4. Quantify the Result
Numbers that tend to strengthen the case:
- Dollar revenue, cost savings, time saved
- p95/p99 latency, error rate, uptime
- Customer adoption count, retention, NPS delta
- People impact: trained N people, unblocked N teams, recruited N hires
- Quality: reduced bugs/incidents/escalations by N
If you cannot quantify, a common approach is to qualify with a credible reference: "shipped on schedule despite a mid-quarter team reorg" — something your manager can verify.
5. Rehearse your top 3 verbally
In the review meeting, you likely won't read all 8 STAR entries — most people get 1-2 chances to speak. Many find it helps to have their three strongest accomplishments ready as 30-second verbal stories.
6. Submit early if your company has a self-review form
Self-reviews submitted last often get skimmed; ones submitted first tend to set the frame a manager writes against. Some people choose to submit early for that reason.
What red flags should you watch for?
The red flags in a review are mostly signs that the conversation is not tracking the year. A manager with nothing specific to say about your impact generally did not track it, and many people find their own STAR document quietly ends up doing both jobs. A conversation that centers on one negative event from 60 days ago while passing over eleven months of solid work is the same problem in a different shape, and a year-spanning list is the usual counter to it. Soft concerns with no measurable bar — "you could be more proactive" — are worth asking to have made specific. A "meets expectations" rating despite clearly-above-bar impact is often budget-driven rather than performance-driven. And a request to sign on the spot is one many people answer by asking for time to add their own comments. What people watch for:
- Your manager has nothing specific to say about your impact (which can suggest they did not track your year — many people find their STAR doc is now doing both jobs, and lean into that)
- The conversation centers on a single negative event 60 days ago and bypasses 11 months of solid work (a common counter is the year-spanning STAR list)
- Your manager raises "soft" concerns that have no clear measurable bar ("you could be more proactive") — many people ask for specificity here
- You receive a "meets expectations" rating despite delivering clearly-above-bar impact (often a budget-driven rating; many people keep STAR data as their appeal evidence)
- You are asked to sign your review on the spot — many people ask for time to add comments
When should you push back?
Pushing back is generally worth it when a review materially understates impact you have evidence for — the evidence is what makes the conversation possible, and without it a disagreement is just two impressions of the same year. The usual first step is asking for a follow-up 1:1 about the rating rather than arguing in the review meeting itself. If that does not move anything, most HR systems allow a written addendum or employee comments, which puts your account in the file alongside the rating. A skip-level escalation is the step people take next when a manager will not engage at all. Where the concern involves a protected class — peers rated higher for parallel impact — documenting the disparity comes first, and some people then talk to HR or an employment attorney. Which of these is worth doing depends on the facts. Common steps people take:
- Requesting a follow-up 1:1 to discuss the rating
- Submitting a written addendum to the review (most HR systems allow employee comments)
- Escalating to skip-level if a manager won't engage
- For protected-class concerns (e.g., peers' work rated higher despite parallel impact), documenting the disparity and considering talking to HR or an employment attorney. The EEOC explains that, under federal laws like the Equal Pay Act, Title VII, the ADEA, and the ADA, compensation and pay decisions are generally protected from discrimination based on characteristics such as sex, race, color, religion, national origin, age (40+), or disability — though whether any of this applies depends on your specific situation, and state law may add protections.
Official sources
- U.S. Equal Employment Opportunity Commission — Facts About Equal Pay and Compensation Discrimination
- U.S. Equal Employment Opportunity Commission — Employees & Job Applicants