How to write performance review accomplishments that actually get read
Short answer
Each accomplishment is one paragraph: lead with the metric, name the work, end with the business impact. Don't bury the result. Don't list everything. Three to five accomplishments, each with a number and a business outcome, beats a wall of bullet points. If you can't quantify an item, either find the proxy metric or cut it.
You're here because
- Your accomplishments section is open and you're staring at the cursor
- You did meaningful work but can't make it sound meaningful
- You're worried bullet-point lists undersell what you did
- You don't know how to write impact without bragging
- You want a structure you can apply to any accomplishment in 5 minutes
The exact email to send
The structure (one paragraph each):
Metric → Work → Business outcome.
Before (typical):
"Led the migration project. Worked with engineering and product to move the platform to the new infrastructure. The project went well."
After (STAR + metric + outcome):
"Reduced platform infrastructure costs by 31% ($420K annualized) by leading the migration off the legacy hosting setup. Coordinated 4 engineers and 2 product stakeholders across an 11-week timeline, hit the original launch date with zero customer-facing downtime, and freed roughly ~120 engineer-hours/month from incident toil."
Three more before/after rewrites:
Before — "Wrote the new onboarding documentation."
After — "Cut new-hire ramp time from 6 weeks to 3.5 weeks by rebuilding the onboarding doc with role-specific tracks. Used by 14 new hires in the period, freeing roughly 1 day/week of senior engineer time previously spent answering setup questions."
Before — "Improved customer reporting."
After — "Cut weekly reporting time from 6 hours to 45 minutes by building the automated customer-health dashboard. Replaced 3 manual reports, freed ~20 hours/month of CS time, and gave account leads same-day visibility into churn signals."
Before — "Mentored junior engineers."
After — "Mentored 3 junior engineers through their first solo on-call rotation. Each passed their first 6-week review, two have since been moved to higher-impact projects, and the team's average on-call response time dropped 12%."
- Built for the moment a written offer or deadline lands — not casual browsing.
- Written for the 24–72 hour decision window.
- Designed for people who don't negotiate often.
- Real workplace register — not internet bravado.
What NOT to say
- "Worked on X" — replace with the outcome of working on it.
- Vague descriptors ("significantly," "meaningfully"). Use the number.
- Long timeline narratives. Calibration skims; lead with the metric.
- Crediting the entire team without naming your contribution. Both: credit the team, name your role.
- Listing 10+ accomplishments. Three to five sharp ones beat a long mediocre list.
An illustrative example
Rewrote four accomplishments using the metric → work → outcome structure. Sent it to skip-level a week before calibration. Skip-level pulled the exact phrasing into the calibration discussion. The manager moved from Meets to Exceeds, with a +14% comp adjustment and earlier promo eligibility. The phrasing did the work — the underlying achievements were the same as the year before.
Why this works
Performance reviews are evaluated under time pressure. A reader who can answer "what did this person do?" in 5 seconds from the first sentence will rate higher than one who has to mine the paragraph for the result. Lead with the metric, and you give every reader the answer immediately.
What to do next
Apply the structure to your accomplishments today. The Performance Review Kit includes the STAR template, the goal-setting wording for next cycle, and the manager-feedback request — so the evidence keeps building for the next review, not just this one.
Before you send — quick check
- Have you listed 3 outcomes in STAR format with numbers?
- Have you mapped them to the next level's scope?
- Have you removed every adjective ("great", "strong") and replaced with metrics?
If you answered "not sure" to any of these, the Performance Review Kit walks you through all three.
Related reads
FAQ
What if my role doesn't have obvious metrics?
Use proxy metrics: stakeholders served, hours saved, errors reduced, quality scores, throughput, lead time. Almost every role has measurable signal — it takes 10 minutes to find.
How many accomplishments should I include?
Three to five. Above five, calibration starts skimming. Below three, the case feels thin.
Should I quantify mentorship and influence work?
Yes. "Mentored N people" with an outcome (passed review, took on harder work, increased team throughput) is calibration-readable. Don't skip it because it feels soft — quantify it.