Most people treat the self performance review as a bureaucratic box to tick.
You're given a form, a deadline, and a rough memory of the last six months, and you're expected to produce something meaningful. Most people either undersell themselves out of habit or copy-paste generic phrases from a template.
Neither approach actually helps you 😵💫
A well-written self review does three things: it shows your manager what you've contributed, it positions you for the conversations you want to have (about growth, compensation, and role), and it creates a record of your own progression. Done right, it's genuinely worth the hour it takes.
Here's what good looks like, with examples you can actually use.
What a good self performance review actually covers
Before getting to the examples, it's worth understanding the structure. Most self reviews ask you to address three things:
- What did you accomplish? (outcomes and output, delivery)
- How did you work? (behaviours, collaboration, approach)
- What's next? (growth areas, goals, development)
The mistake most people make is answering the first question only. They list what they shipped or delivered, and nothing else.
But the 'how' and 'what's next' are often what your manager is most interested in, especially for promotion conversations.
Keep your examples specific. Specific examples are more credible than general claims. "I improved team communication" means nothing. "I introduced a weekly sync that reduced back-and-forth in our design reviews by about half" means something.
Self performance review examples by skill area
Here are ready-to-use examples organised by the skills most commonly assessed. Adapt the specifics to your context.
Communication
"I prioritised proactive communication this quarter, particularly during the product launch in March. I sent weekly status updates to stakeholders before they asked, which helped us avoid two escalations that had happened in the previous quarter."
"I've worked on being more concise in written communication. Earlier in the year, my updates were longer than they needed to be. I've improved, though I know I still default to over-explaining when I'm uncertain."
"I facilitated three cross-functional sessions this quarter, including the planning kickoff and two retrospectives. Feedback from participants was positive, with several noting the sessions stayed focused and on time."
Collaboration
"I collaborated closely with the marketing team on the Q2 campaign. I made myself available for unplanned questions and shared my team's context openly, which helped them make faster decisions."
"There were times this quarter where I could have brought the engineering team into scoping conversations earlier. I recognised this mid-quarter and changed my approach. The last two projects ran more smoothly as a result."
"I contributed to onboarding three new team members, including pairing sessions, documentation reviews, and check-ins during their first month. All three have said they felt well-supported."
Execution and delivery
"I delivered all four of my committed projects this quarter on time and within scope. The exception was the data migration, which ran two weeks over. I've reflected on why and have adjusted my estimation approach for Q3."
"I completed 14 of 16 planned initiatives this quarter. The two that didn't close were deprioritised due to a company-wide pivot, not scope creep or delays on my end."
"I shipped the self-service onboarding feature two weeks ahead of schedule by identifying a simpler technical approach earlier in the sprint than planned."
Leadership and influence
"I took on an informal mentoring relationship with two junior analysts this quarter. I met with them fortnightly and reviewed their work when needed. Both have since taken on more independent projects."
"I advocated for a change in our approach to quarterly planning, specifically moving from a document-heavy process to a lighter OKR format. The change was adopted and the planning cycle was shorter and clearer this quarter."
"I could have been more decisive in the early stages of the rebrand project. I deferred to others when I had a clear point of view and should have shared it. I'll be working on this in Q3."
Learning and growth
"I completed the product analytics certification I'd set as a goal for this half. I've already applied the segmentation techniques in two product decisions."
"I expanded my knowledge of our enterprise customer segment by attending four customer calls outside my normal remit. This has changed how I think about our roadmap priorities."
"Growth was slower this quarter than I'd hoped. I set ambitious learning goals and didn't progress as far as I planned. I've been more realistic in setting Q3 goals."
Self performance review examples by performance level
Sometimes the hardest part isn't finding the words. It's finding words that accurately reflect how the quarter actually went. Here are examples at three levels.
Strong quarter (exceeds expectations)
"This was one of my strongest quarters. I delivered ahead on my primary objective, contributed meaningfully to two cross-functional initiatives outside my remit, and started building the leadership behaviours my manager and I had identified as development areas."
"I hit all four of my key results this quarter, three of them ahead of schedule. More importantly, I think the way I worked, being proactive, transparent, and consistent, set a good example for newer members of the team."
Solid quarter (meets expectations)
"I delivered what I said I would. There were no surprises, no missed commitments, and no quality issues. That said, I don't feel like I stretched myself this quarter and I want that to change."
"I met my core objectives and contributed reliably to team projects. I'm satisfied with my execution but aware that I stayed mostly in familiar territory. Next quarter I want to take on something that pushes me."
Difficult quarter (developing or below expectations)
"This quarter was harder than I'd like to admit. I underestimated the complexity of two projects and missed a deadline that affected the team. I've spoken with my manager about what happened and have put a more realistic planning approach in place."
"I didn't hit my targets this quarter. The reasons are partly external (the org change created real uncertainty) and partly on me. I should have flagged the blockers earlier. I'm not proud of the outcome, but I have a clearer plan for Q3."
How to write yours honestly
The hardest self reviews to write aren't the ones where you've had a great quarter. They're the ones where you know you fell short, or where you're not sure what you actually contributed.
A few principles that help:
- Be specific about what was in your control. You can acknowledge external factors (a reorg, a delayed dependency, a market shift) without hiding behind them. Separate what happened from what you did about it.
- Acknowledge gaps directly. Managers notice when self reviews are uniformly positive. A well-placed honest reflection, 'I took on too much and it showed in my quality of output,' actually builds more trust than a polished narrative that pretends nothing went wrong.
- Tie your examples to outcomes. 'I worked hard on X' is less useful than 'X moved from 0 to 60% complete and is on track to close in Q3.' Results create context. If you don't know your outcomes, that's a gap worth fixing.
Not sure what good looks like for your role? Looking at performance goals examples before you write your self review helps you calibrate what 'strong' actually means at your level.
- Use your check-ins as source material. If you've been tracking your goals regularly, your self review largely writes itself. Your weekly updates already have the milestones, the blockers, the progress notes. It's a much better starting point than trying to reconstruct the last six months from memory.
How goal tracking changes the self-review
One of the biggest reasons self reviews feel hard is that most people write them from memory. Six months of work, distilled in an afternoon, under deadline pressure.
The alternative is to track your work goals as you go. Weekly or fortnightly check-ins against your objectives mean that by the time review season arrives, you have a record: what you planned, what actually happened, where you got stuck, and what you adjusted.
Tools like Tability are built for exactly this. You set your goals at the start of the quarter — whether you're running personal OKRs or team-level goals — check in regularly, and add brief notes when things shift. By the time your self review is due, you can review a quarter of structured progress instead of relying on a rough mental summary. The examples above are useful starting points. But the strongest self reviews are built from real data, not templates.
Goal tracking software for performance reviews
If your team doesn't have a structured way to track goals and check in regularly, your self reviews will always be harder than they need to be. Tability gives individuals and teams a lightweight way to set OKRs, track progress, and build the record that makes performance conversations straightforward.
Sign up free or book a 30-minute chat to see what it looks like for your team.
.png)
.jpg)
.png)
