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?
Many people write 2-4 sentences per accomplishment in this shape:
- 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?
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?
- 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?
When a review materially understates impact someone has evidence for, common steps people take include:
- 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