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.
STAR — Situation, Task, Action, Result — 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.
The structure
For each accomplishment, write 2-4 sentences 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.
Step-by-step: what to do
1. Pull the year's signals into one document
Block 2 hours. 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, your own brag doc if you have one. List the 10-20 things you actually did. Don't filter yet.
2. Filter to the top 5-8 that map to your level/role expectations
For each accomplishment, 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 they shouldn't crowd out items that do.
3. Write each as STAR
Keep it tight. Each STAR should fit in 4-5 lines max. If you need more, you are probably blending two accomplishments.
4. Quantify the Result
Numbers that 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, qualify with a credible reference: "shipped on schedule despite a mid-quarter team reorg" — your manager can verify.
5. Rehearse your top 3 verbally
In the review meeting, you will not read 8 STAR entries. You will get 1-2 chances to speak. Have your three strongest accomplishments ready as 30-second verbal stories.
6. Submit early if your company has a self-review form
Self-reviews submitted last get skimmed. Self-reviews submitted first set the frame your manager writes against.
Red flags to watch for
- Your manager has nothing specific to say about your impact (suggests they did not track your year — your STAR doc is now doing both your job and theirs, and that is fine, lean in)
- The conversation centers on a single negative event 60 days ago and bypasses 11 months of solid work (counter with the year-spanning STAR list)
- Your manager raises "soft" concerns that have no clear measurable bar ("you could be more proactive") — push for specificity
- You receive a "meets expectations" rating despite delivering clearly-above-bar impact (often a budget-driven rating; STAR data is your appeal evidence)
- You are asked to sign your review on the spot — you can ask for time to add comments
When to push back
If your review materially understates impact you have evidence for:
- Request a follow-up 1:1 to discuss the rating
- Submit a written addendum to the review (most HR systems allow employee comments)
- Escalate to skip-level if your manager refuses to engage
- For protected-class concerns (e.g., your peers' work is rated higher despite parallel impact), document the disparity and consider talking to HR or an employment attorney
Educational content only — not legal or HR advice. Practices vary by employer. Adapt to your team's review process.