HomeResourcesSTAR Method Examples for Performance Reviews

STAR Method Examples for Performance Reviews

How to use the STAR method in a self-review, not just interviews: six examples across roles, a fill-in template, and what to do without numbers.

4 min read

The STAR method is usually taught as interview prep. It's just as useful in a performance review, where the problem is the same: you need to describe one piece of work so that someone who wasn't there understands what happened and why it mattered.

This guide shows how STAR fits a self-review, with six examples from different roles you can adapt.

What STAR means

  • Situation: the context. What was going on?
  • Task: what needed to happen, and what part was yours?
  • Action: what you did. This is the heart of it.
  • Result: what changed because of it.

In interviews, people often spend most of their time on the situation. In a self-review your manager already knows the context, so keep Situation and Task short and spend your words on Action and Result.

How STAR in a review differs from STAR in an interview

InterviewPerformance review
ReaderA strangerYour manager, who knows the context
SituationNeeds setupOne sentence is enough
ProofYour wordCan be checked, so it must be accurate
LengthSpoken, 1-2 minutesWritten, 3-5 sentences

Because your manager can check the details, accuracy matters more than drama. A modest true result beats an impressive invented one.

Six STAR examples for performance reviews

These are illustrative examples. Replace the details with your own and keep only numbers you can show.

1. Operations: fixing a slow approval process

Situation: Vendor invoices needed sign-off from three teams and approvals often stalled in email.

Task: I was asked to make approvals predictable before month-end close.

Action: I mapped where invoices got stuck, built a single approval sheet with owners and due dates, and walked each approver through it.

Result: Approvals moved to one place and finance stopped chasing sign-offs by email; average approval time went from about [X] days to about [Y].

2. Product: shipping under a late change

Situation: Two weeks before the pricing page relaunch, legal asked for copy changes.

Task: Keep the launch date without skipping the legal review.

Action: I re-sequenced the design work, set a daily 15-minute check-in for the final two weeks, and got legal's sign-off on each section as it was ready instead of at the end.

Result: The page launched on the planned date with legal approval.

3. Engineering: a recurring failure

Situation: The nightly export job failed a few times a week and someone had to rerun it by hand.

Task: Find the cause and stop the manual reruns.

Action: I traced the failures to a timezone bug in the date filter, fixed it and added a regression test.

Result: The job has run without manual reruns since the fix.

4. Customer success: saving an at-risk account

Situation: A long-time customer's usage dropped and their renewal was coming up.

Task: Understand why and make the renewal decision easier for them.

Action: I set up a call with their new admin, found they'd never been trained on the reporting feature, ran two short training sessions and shared a one-page guide.

Result: Their team started using reports again and they renewed.

5. Marketing: fixing a broken handoff

Situation: Leads from webinars sat for days before sales saw them.

Task: Get webinar leads to sales faster.

Action: I worked with sales ops to route webinar sign-ups straight into the CRM with an owner assigned, and set up a weekly check of unassigned leads.

Result: Webinar leads now reach a sales rep the same day.

6. Any role: onboarding a teammate

Situation: Our team hired two people in the same month and had no written onboarding.

Task: I volunteered to get them productive without pulling the whole team into training.

Action: I wrote a first-week checklist and context doc, paired with each of them for an hour a day in week one, and collected their questions into an FAQ.

Result: Both took on their own work in their second week, and the checklist is now used for every new hire.

Fill-in STAR template for your self-review

[Short title of the work]

Situation: [One sentence of context]
Task: [What needed to happen and what part was yours]
Action: [What you did, in order. Use "I".]
Result: [What changed. Real number if you have one, plain description if not.]

Three common mistakes

  1. "We" everywhere. Your manager wants to know your part. Say "we" for the team effort and "I" for what you did.
  2. A result that is really an action. "Launched the new flow" is an action. The result is what happened after: fewer tickets, faster setup, a renewal.
  3. Made-up metrics. If you write "improved efficiency by 40%", be ready to show where 40% came from. If you can't, describe the change instead.

Build your STAR stories as you go

The best STAR stories come from notes written the week it happened, when you still remember the details. A sentence or two each Friday is enough raw material. If you already send a weekly status update, each "Done" line is a STAR story waiting to be written.

To turn one of those notes into a STAR story now, paste it into the free STAR method generator. It only uses what you wrote, so there are no made-up numbers to defend. For role-specific wording, see the product manager self-evaluation examples and the other examples by role.

Free tool · No sign-up

Turn one work note into a STAR story

Paste a sentence or two about something you did. You get a STAR story and a resume bullet that only use what you wrote.

Try the STAR generator

Frequently asked questions

Is the STAR method only for interviews?

No. It works anywhere you need to describe one piece of work clearly: self-reviews, promotion packets, peer feedback and 1:1s. In a review it helps your manager see the problem, your part and the outcome without extra questions.

How long should a STAR example be in a self-review?

Three to five sentences. One for the situation and task together, one or two for your actions, and one for the result. Longer stories belong in a linked doc.

What if the result isn't measurable?

Describe the change in plain words: who stopped being blocked, what got easier, what risk went away. A specific, honest description is stronger than a guessed percentage.

How many STAR examples should I use?

Pick three to five that match what your review form or your manager cares about most. Use bullets for everything else.

Write it down this week. Use it at review time.

WinStash keeps a short note from each week and turns your notes into a weekly update, a brag sheet and STAR stories, using only what you wrote.

Start free on WinStashFree plan · No credit card required

Keep reading

Self-evaluation examples by role: Operations Manager · Project Manager · Marketing Manager · Account Executive · Customer Success Manager · UX Designer