Performance Review Examples, Written With the STAR Method

The hard part of a performance review is rarely the writing — it's remembering what you actually did, and saying it in a way a manager can act on. Below are six worked examples, each starting from the kind of rough note people really jot down, then rewritten as situation, task, action, and result. Nothing in them is invented; every example only reorganizes what the note already contained.

The STAR structure behind every example

Situation

The context your manager needs: the team, the timeframe, and what was going wrong or at stake.

Task

What you were specifically responsible for — separate your ownership from the team's.

Action

The concrete steps you took, in your own words. Verbs, not adjectives.

Result

What changed, with a number where you have one. Leave it out rather than estimating.

Six performance review examples

Adapt the shape, not the facts. Swap in your own situation and keep any metric you can actually stand behind.

Delivery and execution

Rough note → review entry

What you'd jot down

"shipped the billing revamp late but it went fine"

The review entry

Situation: The billing revamp was two sprints behind and blocking three downstream teams from releasing.

Task: I owned the migration plan and the release sequencing.

Action: Cut the release into three shippable stages, moved invoice generation first, and ran a daily fifteen-minute unblock with the dependent teams.

Result: All three teams unblocked within a sprint, and the full revamp shipped with no customer-facing billing incidents.

0 billing incidents at launch

Delivery planningCross-team coordinationRisk reduction

Impact with a number

Rough note → review entry

What you'd jot down

"rewrote the onboarding docs, new hires ramped faster"

The review entry

Situation: New hires relied on scattered, outdated onboarding material spread across four documents.

Task: I volunteered to consolidate onboarding for the team.

Action: Rewrote the material into a single guided path and paired it with a first-week checklist reviewed by the two most recent hires.

Result: Time to full productivity dropped from six weeks to four for the next three hires.

33% faster ramp time

DocumentationProcess improvementOnboarding

Leadership without the title

Rough note → review entry

What you'd jot down

"kind of ran the incident when the lead was out"

The review entry

Situation: A production outage hit during a week when the on-call lead was unavailable.

Task: I stepped in to coordinate the response.

Action: Ran the incident channel, assigned investigation lanes, published updates every twenty minutes, and wrote the postmortem with three follow-up actions.

Result: Service was restored the same morning and all three follow-ups were closed that month.

Restored same day

Incident responseCommunicationOwnership

Collaboration and influence

Rough note → review entry

What you'd jot down

"got support and eng to stop arguing about bug triage"

The review entry

Situation: Support and engineering disagreed about bug priority, and urgent tickets sat untouched for days.

Task: I proposed and facilitated a shared triage process.

Action: Wrote a one-page severity rubric with examples from real tickets, walked both teams through it, and set up a weekly joint triage.

Result: Escalations were acknowledged within one business day instead of drifting for a week.

1-day acknowledgement

Stakeholder alignmentPrioritizationFacilitation

Growth and learning

Rough note → review entry

What you'd jot down

"got better at the data side this year"

The review entry

Situation: Reporting requests kept queuing behind the analytics team, delaying my own decisions.

Task: I set out to handle routine analysis myself.

Action: Completed a SQL course, rebuilt the team's weekly report as a self-serve dashboard, and documented the queries for teammates.

Result: Routine reporting requests to the analytics team stopped, and the team reads the dashboard weekly.

Self-serve weekly reporting

SQLSelf-directionEnablement

An area to improve, written well

Rough note → review entry

What you'd jot down

"i take on too much and it slows things down"

The review entry

Situation: I accepted work from three parallel projects last quarter, and two of my commitments slipped.

Task: I need to protect focus on my primary deliverables.

Action: Started reviewing new requests against current commitments before saying yes, and now surface tradeoffs to my manager instead of absorbing them.

Result: Since making the change I have met every committed date on my primary project this quarter.

On-time delivery restored

PrioritizationSelf-awarenessExpectation setting

Stop rebuilding your review from memory

EverUpward turns a rough sentence into exactly the structure above — situation, actions, result, metrics, and skills — and flags what's missing instead of inventing it. Each entry is filed in a numbered, permanent Career Vault you add to all year, so review season becomes a matter of choosing evidence rather than recalling it.

Build Your Career Vault

Performance review questions

What should a performance review example actually include?

A situation with enough context to matter, the part you personally owned, the actions you took, and a result. Anything you can measure belongs in the result; anything you cannot measure is better described plainly than estimated.

How many examples should I bring to a review?

Five to eight strong examples spread across your main responsibilities is usually enough for an annual review. Depth on a few real accomplishments beats a long list of tasks.

What if I do not have numbers?

Describe the before and after in concrete terms instead: what people had to do previously, and what they do now. Never invent a percentage — a fabricated number is the fastest way to lose credibility in a review conversation.

How do I write the 'areas for improvement' section?

Name a specific pattern, not a personality flaw, then show the change you already made and any early evidence it is working. That reads as self-awareness rather than an apology.

How do I remember all of this at review time?

Write each accomplishment down when it happens. That is exactly what the EverUpward Career Vault is for: a permanent, numbered record you add to throughout the year, so review season is a matter of selecting evidence rather than trying to recall it.

Related: brag sheet template for documenting accomplishments as they happen.