Back to blog

How to Explain Your Work in a Performance Review in English

2026-07-09

A performance review is not the time to list every task you completed.

It is the time to make your work legible.

Too small:

"I worked on the onboarding project."

Too broad:

"I contributed to many initiatives."

More professional:

"I owned the onboarding handoff workstream. The impact was fewer repeated client questions after kickoff, and the evidence is that support escalations dropped in the first two weeks."

Explaining your work well means naming ownership, scope, impact, trade-offs, evidence, and the next growth area.

Start with ownership

Ownership clarifies your role in the work.

Useful phrases:

Examples:

"I owned the onboarding handoff workstream."

"I drove the cross-functional work to clarify implementation ownership."

"My main contribution was translating customer feedback into a clearer product requirement."

For more on this distinction, see Ownership vs Accountability: How to Use Them Naturally in Professional English.

Name the scope

Scope helps the listener understand the size and boundaries of the work.

Useful phrases:

Examples:

"The scope was the post-kickoff handoff for enterprise customers."

"The scope expanded from a reporting update to a full workflow redesign."

"This involved product, customer success, and implementation."

Scope prevents meaningful work from sounding like a small task.

Explain the impact

Impact explains why the work mattered.

Useful phrases:

Examples:

"The impact was fewer repeated ownership questions from clients."

"One result was faster response time during the first week after launch."

"What changed was that implementation had a clearer owner for each handoff."

For related language, see How to Explain Impact in English Without Sounding Dramatic.

Include the trade-off

Performance reviews are stronger when you show judgment, not only results.

Think you know this expression?

Take the free 2-minute High-value Workplace Expression Gap Test and see which expressions you should practice.

Take the free challenge →

Useful phrases:

Examples:

"The trade-off was reducing phase-one reporting so we could protect launch quality."

"I prioritized clarity over speed because the client handoff risk was higher than the timing risk."

"One constraint was support capacity during renewal season."

Trade-off language shows that you understand the decision context.

Ground the impact in evidence

Evidence makes your contribution easier to evaluate.

Useful phrases:

Examples:

"The evidence is that support escalations dropped during the first two weeks after rollout."

"The strongest signal was that clients asked fewer ownership questions after kickoff."

"The evidence suggests the new process reduced handoff friction."

For related calibration, see Evidence vs Proof: How to Use Them Naturally in Professional English.

Name the next growth area

A strong review can include growth without making the whole story smaller.

Useful phrases:

Examples:

"One area I am still developing is communicating risks earlier when scope starts to change."

"The next area I want to strengthen is executive-level recommendation framing."

"Going forward, I want to improve how I connect customer evidence to product priorities."

Growth language is strongest when it is specific.

A practical structure

Use this structure:

"I owned [work/scope]. The impact was [impact]. The trade-off was [trade-off]. The evidence is [evidence]. One area I am still developing is [growth area]."

Example:

"I owned the onboarding handoff workstream for enterprise customers. The impact was fewer repeated client questions after kickoff. The trade-off was that we kept the first version simple rather than solving every edge case. The evidence is that support escalations dropped in the first two weeks. One area I am still developing is communicating scope risk earlier when the handoff changes."

That sounds complete without sounding inflated.

Common mistakes

Mistake 1: Listing tasks instead of impact

Too small:

"I attended meetings and updated the process."

More useful:

"I drove the process update that reduced repeated handoff questions after kickoff."

Tasks show activity. Impact shows value.

Mistake 2: Using "we" when your role needs clarity

Vague:

"We improved onboarding."

More precise:

"I owned the client handoff workstream within the broader onboarding improvement."

Use "we" for team outcomes, but clarify your contribution.

Mistake 3: Naming growth too generally

Too broad:

"I want to improve communication."

More professional:

"I want to improve how I frame trade-offs for leadership before decisions are made."

Specific growth sounds more credible.

Practice scenarios

Practice explaining your work in performance-review moments like:

Useful practice phrases:

That is the kind of workplace expression Lyra Practice helps advanced professionals practice: performance-review language with ownership, evidence, and professional fit.

A performance review should not make your work sound bigger than it was.

It should make the value of the work easier to see.

Lyra Practice helps advanced non-native English professionals learn the nuance of high-value workplace expressions and practice using them in realistic scenarios, so their English sounds natural, precise, and senior at work. Try Lyra Practice.

Think you know this expression?

Take the free 2-minute High-value Workplace Expression Gap Test and see which expressions you should practice.

Take the free challenge