Performance Review Vocabulary in English
CEFR B1-B2 • Business English • Self-review writing, feedback wording, and the strength/weakness phrases that work
Why performance-review English is its own dialect
Performance reviews use a specific vocabulary that differs from everyday business English. The verbs are stronger ("delivered," "drove," "led"). The framing is structured (situation, action, result). And the strength/weakness sections follow patterns native speakers know without thinking. If you are a non-native speaker writing your first English self-review, this is the page to read before you open the form.
This guide covers the 50 phrases and patterns you need: STAR structure, action verbs, growth-area framing, manager feedback wording, and what NOT to say.
The STAR pattern: how to structure every accomplishment
Every strong achievement in a self-review follows the same four-step pattern, called STAR.
| Letter | Means | Example sentence |
|---|---|---|
| S Situation | The context or problem | "Our checkout error rate had been climbing for three months." |
| T Task | What you needed to do | "I owned the investigation and proposed a fix path." |
| A Action | What you actually did | "Instrumented the flow with tracing, identified the root cause in the payment retry loop, and shipped a fix in three weeks." |
| R Result | The measurable outcome | "Error rate dropped from 4.2% to 0.3%, recovering an estimated $180k in lost revenue per quarter." |
Pro tip: if your accomplishment does not have a measurable Result, the reviewer cannot give you full credit. Numbers, percentages, dollar amounts, time saved, customers retained — pick whatever metric fits and put it in.
Action verbs: the words that make achievements land
Replace weak verbs ("did," "worked on," "helped with") with strong ones. Click to hear the rhythm.
"Drove the migration of 12 services from on-prem to AWS, completing six months ahead of plan."
"Drove" = led with high ownership. Top-tier achievement verb.
"Spearheaded the cross-functional effort to redesign the onboarding flow."
"Spearheaded" = led from the front. Strong but not arrogant.
"Delivered the Q3 product launch on the original schedule despite mid-quarter scope changes."
"Delivered" emphasizes finishing, not just starting.
"Mentored two junior engineers — both promoted to senior level by year-end."
"Mentored" + tied to outcome = strongest framing for people-development.
"Streamlined the deployment pipeline, reducing release cycle time from 5 days to 6 hours."
"Streamlined" = simplified for efficiency. Pair with measurable result.
"Negotiated a 15% discount on the data-warehouse contract, saving $240k annually."
"Negotiated" needs a number — that is what makes it land.
"Established the engineering on-call rotation, reducing P1 incident response time by 40%."
"Established" = built from nothing. Strong for new processes.
Strengths section: how to praise yourself without sounding arrogant
Calibrate the strength to a specific, measurable example. Vague claims ("I am a great team player") are worthless. Click to hear how to phrase it well.
"My core strength this year has been cross-functional execution — partnering with sales, marketing, and engineering to ship the Acme renewal motion."
"Core strength" + named example = credible.
"I have consistently delivered on customer-facing commitments, with NPS scores rising from 42 to 58 across the quarter."
"Consistently" + metric = trustworthy claim.
"One area I have particularly leaned into is mentoring — formally onboarding three new hires this year."
"Leaned into" = invested deliberately. Modern, modest verb.
Growth areas: how to admit weakness without hurting yourself
This is where most non-native speakers either over-confess or skip the section entirely. Both are mistakes. The pattern is: name the gap, name the action, name the proof.
| Pattern | Example |
|---|---|
| Name the gap (specifically, not "I am bad at X") | "My presentation skills to executive audiences need development." |
| Name the action you are taking | "I have signed up for a Toastmasters group and am presenting monthly." |
| Name the early proof | "Initial feedback from my Q4 board prep session was directly actionable." |
What NOT to say: "I am a perfectionist" or "I work too hard." These are non-answers and reviewers see right through them. Name a real gap. Show the work.
Frame growth areas with these openers
"An area I want to invest in this year is technical depth in distributed systems — I have started the Coursera specialization and applied lessons in two design docs already."
"Invest in" frames it as growth, not weakness.
"Looking ahead, I want to develop my ability to give critical feedback to peers — I tend to soften too much."
"Looking ahead" + specific behavior = credible self-awareness.
"One thing I have been working on is delegating more — specifically, letting Aiyana own the weekly stakeholder update instead of writing it myself."
Specific delegation + named person = real action.
Giving feedback to direct reports
If you manage people, you are also writing reviews FOR them. Use these patterns to keep feedback constructive.
Praise pattern: "What + Impact + Why it matters"
- "Sandeep led the Q3 incident response (what), reducing customer-visible downtime to 12 minutes (impact), which protected our SLA commitment with our top three accounts (why it matters)."
- "Marina spearheaded the new design-review process (what), cutting review cycle time by 60% (impact), which unblocked four teams from a recurring bottleneck (why it matters)."
Constructive feedback pattern: "Behavior + Impact + Suggestion"
- "In design reviews, you sometimes commit to a position before hearing all input (behavior). Two engineers told me they have stopped raising concerns (impact). Try asking 'who has a different view?' before stating yours (suggestion)."
- "You have been holding the team to your weekend pace (behavior). Three people mentioned burnout in skip-level chats (impact). Could you set explicit 'do not message after 7 PM' norms? (suggestion)."
Phrases to ALWAYS avoid in self-reviews
- "I think I did good" → "I delivered on every commitment in my Q1 plan." Vague becomes concrete.
- "I am very hard worker" → "I worked 12 weekends to support the launch." Show, do not tell — but with specifics, not implied virtue.
- "I helped my team" → "I unblocked Aiyana on the auth migration by pairing with her for two days." Name the person, name the contribution.
- "I am sorry I did not do more" → omit. Self-reviews are not the place to apologize.
- "I tried my best" → "I delivered against my goals despite the headcount cut in March." Effort without result is not what reviewers reward.
A complete self-review entry, end-to-end
Goal: Improve checkout reliability — Q3 OKR
What I did:
The checkout error rate had climbed from 1.8% to 4.2% over Q2, primarily affecting our top 100 enterprise accounts. I owned the investigation alongside Carlos from SRE.
We instrumented the full flow with OpenTelemetry, identified the root cause in the payment-retry loop (3 weeks of debugging), and shipped a fix that consolidated retry logic into a single, observable circuit breaker. I also drove the postmortem and wrote our first formal runbook for checkout incidents.
Result:
- Error rate dropped from 4.2% to 0.3% within two weeks of the fix
- Recovered an estimated $180k in monthly revenue (calculated by Finance)
- Runbook adopted by SRE for all customer-facing flows
What I learned:
The original 2-day spike was too short to surface the real problem. Going forward, I will push for 1-week minimums on initial investigations of recurring incidents.
Practice: Test yourself
Tap each question to reveal the answer.