employee recognition, performance, feedback, evaluation,

Self-Evaluation Examples: 50 Phrases, Templates & How to Write One That Actually Works

Stas Kulesh
Stas Kulesh Follow
Jul 01, 2026 · 23 mins read
Self-Evaluation Examples: 50 Phrases, Templates & How to Write One That Actually Works
Share this

Most people approach a self-evaluation the same way: stare at a blank document for twenty minutes, write something vague about “contributing to team goals,” and submit it hoping nobody reads it too closely.

It doesn’t have to work that way. A well-written self-evaluation is one of the best opportunities you have to shape how your manager thinks about your performance — to name what you actually did, put it in context, and articulate where you want to go next. Done well, it’s not a form to fill out. It’s a career conversation you get to write yourself.

This guide covers what a self-evaluation is, how to write one that’s genuinely useful rather than painfully vague, 50 specific examples organised by category, the best keywords and phrases to use, and what to do about areas of improvement without undermining yourself.


In this article

  1. What is a self-evaluation?
  2. How to write a self-evaluation that stands out
  3. 50 self-evaluation examples by category
  4. Areas of improvement: how to write about weaknesses without hurting yourself
  5. Keywords and phrases for self-evaluations
  6. Self-evaluation summary examples
  7. Common mistakes and how to avoid them
  8. How peer recognition data makes self-evaluations easier

What is a self-evaluation?

A self-evaluation (also called a self-assessment, self-appraisal, or self-performance review) is a structured reflection on your own work performance over a defined period — typically a quarter, half-year, or full year. It’s usually a required part of a formal performance review process and is submitted to your manager before or alongside their own assessment of your work.

The purpose of a self-evaluation is threefold. First, it gives your manager information they might not have — context about what you worked on, what you learned, what got in the way, and what you’re planning next. Second, it gives you a structured opportunity to advocate for your own contribution. And third, it creates a written record of your professional development that you can track over time.

Most self-evaluations ask you to cover similar ground: what you accomplished, how you performed against goals, what you’re proud of, where you struggled, and what you want to work on next. The difference between a good self-evaluation and a forgettable one is almost entirely in the specificity of the answers.


How to write a self-evaluation that stands out

Start with evidence, not adjectives

“I am a dedicated and hardworking team member” is meaningless because every person who ever wrote a self-evaluation wrote something like it. “I delivered the API integration three days ahead of the deadline, which gave the QA team additional time to find and fix four critical bugs before launch” is specific, verifiable, and memorable.

The test for every statement in your self-evaluation: could someone who doesn’t know you well read this sentence and understand exactly what you did? If not, it needs more specificity.

Use the CAR structure for accomplishments

For each significant contribution, structure it as:

Context — what was the situation or challenge? Action — what specifically did you do? Result — what was the measurable or observable outcome?

This structure forces you to be concrete rather than abstract. “Improved team communication” becomes “After noticing that our sprint retrospectives were producing the same blockers repeatedly, I proposed and ran a new format that separated process issues from interpersonal ones. In the following quarter, we reduced recurring blockers by roughly half and the retrospective satisfaction rating from the team went from 3.1 to 4.4 out of 5.”

Write about the work, not your feelings about the work

Self-evaluations full of “I felt,” “I believe,” and “I think” are weaker than ones that describe observable events. Your feelings about your performance are not evidence of your performance. The events are the evidence.

Balance honesty with advocacy

A self-evaluation is not the place for false modesty, but it’s also not a list of everything that went wrong. Be honest about areas of improvement — your manager already knows about them and will trust you more if you raise them yourself — but frame them forward: what you learned, what you’re doing differently, what support would help.

Write it in the week before you submit it

Retrospective memory is unreliable. Most people dramatically undercount what they actually did over a year because the beginning of the year feels remote and the recent past dominates. Before writing your self-evaluation, spend 20 minutes going through your calendar, your project management tool, your Slack history, and your inbox to remind yourself what you actually worked on. The list will be longer than you remember.


50 self-evaluation examples by category

Job performance and quality of work

These examples are for the “what did you accomplish” section — the core of most self-evaluations.

1. “This year I led the redesign of our customer onboarding flow, reducing time-to-first-value from 14 days to 6 days. The change contributed to a 12% improvement in 90-day retention for the cohorts onboarded under the new process.”

2. “I delivered all seven projects I owned this quarter on or before their agreed deadlines. In three cases I completed the work early enough to allow additional rounds of review that improved the final output.”

3. “I identified and resolved a data pipeline failure that had been causing incorrect reporting for approximately three weeks without detection. The fix prevented a significant decision from being made on bad data and I documented the root cause to prevent recurrence.”

4. “My work this half focused on technical debt that was slowing the team’s velocity. I refactored four legacy modules that had been causing disproportionate bugs and the defect rate in those areas dropped by approximately 60% in the following sprint cycles.”

5. “I produced 24 pieces of long-form content this quarter, all delivered on brief and on schedule. Three of those pieces became the top-performing organic pages in their respective categories within 60 days of publication.”

6. “I managed a portfolio of seven client accounts this year with no involuntary churn. Two accounts that were at risk in Q1 were retained through proactive relationship management and proposal of new services that addressed their evolving needs.”

7. “I rebuilt the financial model for our pricing review from scratch after identifying that the existing model contained structural errors that would have understated our margin by approximately 15%. The corrected model informed a pricing decision that has contributed meaningfully to Q3 revenue.”

8. “I exceeded my quarterly sales target by 18% in Q2 and 12% in Q3. The outperformance in Q2 was primarily driven by three enterprise deals that I had been developing for over six months; the Q3 results reflect a more diversified pipeline that I deliberately built to reduce dependence on single large opportunities.”


Communication and collaboration

9. “I made a deliberate effort this year to improve how I communicate technical constraints to non-technical stakeholders. I developed a two-page summary format for engineering decisions that has been adopted by two other engineers on the team as their default approach.”

10. “I ran our cross-functional sync between product, engineering, and marketing for Q2 and Q3. The meetings went from consistently running over to finishing five minutes early on average, and two of the four teams involved told me they found the new format significantly more useful than the previous one.”

11. “I proactively shared context that my team needed but that I wasn’t explicitly asked to share — competitive intelligence, client feedback, and market observations that I came across in the course of my work. Several colleagues have mentioned that this made them feel better informed and more confident in their decisions.”

12. “I contributed to three cross-departmental projects this year outside my primary remit. In each case I joined at the request of the project lead rather than being assigned, which I take as a signal that my collaboration style is valued by colleagues in other teams.”

13. “I improved my written communication significantly this year. I moved from sending emails and documents that required follow-up clarification to receiving confirmation that what I produced was immediately actionable. I track this informally by the ratio of ‘thank you, this is clear’ responses to ‘can you clarify’ responses — and the ratio improved markedly in the second half of the year.”

14. “I mediated a disagreement between two team members that was affecting sprint velocity. The situation resolved within two weeks and both people involved have mentioned the outcome positively in subsequent conversations.”


Teamwork and collaboration

15. “I mentored two junior team members this year without it being formally part of my role. Both have taken on significantly more complex work in the second half of the year than they handled in the first, and one has told me directly that our sessions were useful to that growth.”

16. “I consistently took on tasks during crunch periods that fell outside my formal responsibilities — covering for team members on leave, stepping into unfamiliar parts of the codebase when capacity was short, and coordinating handoffs when projects changed ownership. I did this because the team needed it, not because it was asked of me.”

17. “I made a point of giving specific, public recognition to colleagues when their work made a difference to mine. I sent 34 peer kudos this year in our Slack recognition channel — more than any other person in the team — and I believe this contributed to a recognition culture where people feel their work is noticed.”

18. “I actively sought feedback from colleagues rather than waiting for it to be offered. I asked for it after major deliverables, incorporated it into my process, and followed up with the people who gave it to close the loop. This has improved both the quality of my work and my relationships with the people I asked.”

19. “I volunteered to onboard two new team members this quarter. Both told me in their 30-day check-ins that the onboarding experience was better than they had at previous companies, which I attribute in part to the documentation I prepared and the time I invested in their first weeks.”


Initiative and ownership

20. “I identified a gap in our customer feedback process — we were collecting NPS scores but not acting on the qualitative comments in a systematic way. I designed and implemented a lightweight triage process that has produced three product changes in the past quarter, all of which were directly traceable to themes in customer feedback.”

21. “I took full ownership of a project that lost its assigned lead mid-stream. I stepped in without being asked, restructured the remaining work, reset expectations with stakeholders, and delivered the project two weeks behind its original timeline but within the revised one I proposed. The client was satisfied with the outcome.”

22. “I noticed that our internal documentation was consistently out of date and causing confusion and repeated questions. I spent one afternoon per week for six weeks updating and reorganising it. New joiners in the second half of the year have been significantly faster to onboard as a result.”

23. “I ran three experiments this year in my area of work — testing two new approaches to client engagement and one new reporting format. Two of the three experiments produced positive results that I’ve since made standard practice. The third didn’t work and I documented why, so the team doesn’t need to learn the same lesson again.”

24. “I proposed a change to our sprint planning process that I believed would reduce context-switching and improve focus time. The team adopted it on a trial basis, and the results after two sprints were positive enough that it’s now our permanent approach.”


Leadership and influence

25. “I led a team of four for the first time this year. My goal was to delegate meaningfully rather than staying in execution mode, which required conscious effort. By Q3 I had delegated three responsibilities that I had been holding myself in Q1, and all three are being handled at least as well as I was handling them.”

26. “I developed a quarterly priorities framework for my team that replaced a less structured approach. The framework has improved alignment on what matters most and reduced the number of “should we be working on X?” questions I receive by roughly two-thirds.”

27. “I advocated internally for a change that I believed would improve the customer experience, even though it required significant engineering work and was not on the original roadmap. The change was eventually approved and shipped, and customer satisfaction scores for the affected workflow improved by 14 percentage points.”

28. “I represent the engineering team in senior leadership meetings when our manager is unavailable. I’ve done this four times this year and have consistently prepared enough context to represent the team’s perspective accurately and credibly.”

29. “I introduced a peer review process for my team’s outputs that didn’t previously exist. There was initial resistance to the additional overhead, but after two months the team reported that the quality of our work had improved noticeably and the process is now seen as standard.”


Learning and development

30. “I completed three formal certifications this year in areas directly relevant to my role. Each certification corresponded to a gap I had identified in my own skills and has already been applied in my day-to-day work.”

31. “I deliberately sought exposure to parts of the business I didn’t understand well — attending three sales calls, shadowing two customer support sessions, and joining one engineering sprint. The cross-functional understanding I gained has made me significantly more effective in my own role.”

32. “I moved from being uncomfortable with public speaking to running our monthly team presentation without material anxiety. I did this by volunteering for smaller presentation opportunities throughout the year and treating each one as deliberate practice.”

33. “I identified that my weakest area was financial modelling and I did something about it. I completed a self-directed course, applied what I learned to a real project, and received unsolicited positive feedback on the financial section of a proposal that I produced in Q4.”

34. “I asked for feedback after every major deliverable and kept notes on the patterns. The most consistent theme was that my first drafts were strong but my revisions sometimes over-edited and lost the directness of the original. I’ve been working on this and believe my editing judgment has improved in the second half of the year.”


Goal achievement

35. “Of the four goals I set at the start of the year, I fully achieved three and partially achieved one. The partial achievement on the fourth goal was due to a change in company priorities in Q3 that redirected the relevant resources — the goal itself was not abandoned but is now scheduled for completion in Q1 next year.”

36. “I exceeded the primary metric for my role — customer retention rate — by 3.2 percentage points against target. I attribute this to proactive outreach patterns I established in Q1 and maintained throughout the year despite competing priorities.”

37. “I missed my Q2 target for new pipeline generation by 8%. I’ve analysed why: I over-invested in a handful of large opportunities that didn’t close in the quarter and under-invested in building the smaller-deal pipeline that converts faster. I’ve adjusted my approach for Q3 and Q4 accordingly.”

38. “My goal of improving team velocity by 15% was achieved by Q3 — we’re running at approximately 22% above the baseline we measured in Q1. The gains came from a combination of process changes and the elimination of two recurring blockers that I worked with the team to address.”


Areas of improvement: how to write about weaknesses without hurting yourself

Areas of improvement are the section most people dread writing and most managers pay closest attention to. The reason managers pay attention is not to catch you out — it’s to understand whether you have the self-awareness to know where you’re falling short and the agency to do something about it.

The worst approach is either to pretend you have no areas of improvement (which reads as either dishonest or unaware) or to list genuine weaknesses without any forward-looking component (which reads as helpless). The best approach is to be honest about the area, show that you understand why it matters, and describe what you’re already doing about it or what support would help.

Areas of improvement examples

39. “I’ve been slower than I’d like to delegate work that I could hand off. I hold on to tasks longer than necessary because I find it easier to do them myself than to take the time to explain them well. I’m working on this deliberately — in Q4 I’ve committed to handing off at least one meaningful task per week and treating the time invested in briefing colleagues as part of the work, not a cost on top of it.”

40. “My written communication, while generally effective, sometimes lacks the concision that a fast-moving team needs. I write long when I could write short. I’ve started running my most important messages through a self-edit step — asking myself whether each sentence is necessary — and the feedback I’ve received on my recent communication has been noticeably more positive.”

41. “I sometimes struggle to raise concerns early enough. I tend to try to resolve issues myself before escalating, which occasionally means problems reach my manager later than they should. I’m working on recalibrating this — specifically, setting a personal threshold of 48 hours for issues I haven’t resolved myself before escalating.”

42. “My project management is an area where I want to improve. I’m strong in execution but I’ve been inconsistent in keeping documentation up to date and sharing progress proactively. I’ve started using a weekly status update format and the team has responded positively to the increased visibility.”

43. “I’ve found it difficult to give critical feedback directly and in the moment. I tend to let small issues accumulate rather than addressing them as they arise, which means they become harder to address later. I’ve been working on this through deliberate practice in lower-stakes situations — sharing small pieces of feedback immediately rather than waiting for a 1:1 — and I believe my comfort with direct feedback has improved.”

44. “My technical knowledge in [specific area] is shallower than my role requires. I’ve identified this gap and have a plan to address it — I’m currently working through a structured learning programme that I expect to complete by the end of Q1 next year.”

45. “I have a tendency to say yes to more than I can deliver well. This has occasionally meant that I’ve spread myself too thin and produced work that was on time but not at my best standard. I’m working on being more deliberate about prioritisation and more honest about capacity constraints when new requests arrive.”


Keywords and phrases for self-evaluations

These are the phrases that work across most self-evaluation formats — specific enough to be useful, flexible enough to adapt to your context.

For strengths and accomplishments

“Consistently delivered… on time and within scope” — “Took ownership of… without being asked” — “Proactively identified…” — “Contributed directly to… which resulted in…” — “Received positive feedback from [stakeholder] regarding…” — “Improved [metric] from X to Y” — “Led the initiative to…” — “Established a new process for…” — “Exceeded [goal/target] by [amount]” — “Served as the primary point of contact for…”

For teamwork and collaboration

“Collaborated cross-functionally with…” — “Supported colleagues by…” — “Mentored [name/junior team members] on…” — “Volunteered to…” — “Recognised colleagues publicly for…” — “Sought feedback from… and applied it by…”

For initiative and ownership

“Identified an opportunity to improve…” — “Proposed and implemented…” — “Took full ownership of… when…” — “Delivered [project] despite [constraint]…” — “Anticipated [problem] and addressed it before…” — “Designed a new approach to…”

For areas of improvement (forward-looking)

“I recognise that… and am working to address this by…” — “In the next [period] I plan to improve… by…” — “I’ve identified [area] as a development priority and have [action] underway” — “I would benefit from [specific support] to improve…” — “I am actively working on… and have seen [early progress indicator]”

For goals

“Of the goals set at the start of [period], I achieved [X] of [Y]” — “I exceeded the target for [metric] by [amount]” — “The [goal] was partially achieved — the remaining work is planned for [next period]” — “I set a stretch goal of… and reached [outcome]”


Self-evaluation summary examples

A self-evaluation summary is the opening or closing paragraph that gives the overall picture. It should be honest, confident, and forward-looking.

46. Strong year, straightforward summary: “This has been the most productive year of my time at [company]. I delivered on my core goals, expanded my scope into [new area], and invested meaningfully in developing the people around me. The area I most want to focus on next year is [development area] — I have a clear plan and would welcome the opportunity to discuss what support would be most useful.”

47. Solid year with a clear development area: “I achieved three of my four goals this year and made meaningful progress on the fourth, which was disrupted by [external factor]. My strongest contributions were in [area 1] and [area 2]. The place where I want to grow most is [area] — I’ve been honest with myself about why it’s been a gap and I have a specific plan for addressing it in the next cycle.”

48. Challenging year, honest framing: “This year was harder than expected — [brief honest reason] — and my performance reflected that in [specific way]. I’m proud of [genuine accomplishment despite difficulty]. I’ve learned [specific lesson] and I’m approaching the next period differently, specifically by [concrete change]. I’d welcome the chance to discuss both the challenges and the plan openly.”

49. Strong year with leadership growth: “This year marked a shift in how I work — from individual contributor to someone who makes others more effective. I’m proud of [specific contribution] but I’m equally proud of [specific way you helped someone else grow]. The work I do through colleagues and not just by myself feels like the most important development of this period.”

50. Early-career, first full-year evaluation: “This is my first full year at [company] and I’ve prioritised learning as much as delivering. I’ve contributed meaningfully to [specific area], built strong working relationships across [teams/functions], and identified clearly where I need to develop further. I’m proud of [specific achievement] and I’m genuinely excited about what the next year could look like with [specific goal or opportunity].”


Common mistakes and how to avoid them

Vague language without evidence. “I am a strong communicator” and “I work well in teams” are what everyone writes. They carry no information because they’re unverifiable. Every claim needs at least one specific example.

Listing responsibilities instead of accomplishments. “I managed social media accounts and created content” describes a job description, not a performance. “I managed social media accounts and grew organic engagement by 34% year-over-year through a shift to video-first content” describes what you actually achieved.

False modesty. Some people deliberately understate their contributions, believing it will come across as humble. It doesn’t — it comes across as either unaware or dishonest. Your manager knows roughly what you did; if you understate it, they’ll notice the gap.

Excessive self-criticism. The opposite problem: spending disproportionate space on what went wrong without any context, learning, or forward-looking plan. Areas of improvement should take roughly 20–30% of the space — honest but not self-defeating.

Copying generic phrases from the internet. Phrases like “I am a results-driven professional with excellent communication skills” were clichéd ten years ago. If your self-evaluation contains phrases you’ve seen on a hundred other CVs, rewrite them in your own language.

Not asking for what you want. The self-evaluation is one of the few formal opportunities to state what you want from the next period — a new project, a promotion, a development opportunity, a change in scope. Most people don’t use it. Put what you want in writing.


How peer recognition data makes self-evaluations easier

One of the most practical challenges of writing a self-evaluation is remembering what you actually did. A year is a long time and retrospective memory systematically underweights the first half.

If your team uses a peer recognition platform like Karma, your recognition feed is a searchable record of contributions that colleagues noticed and chose to name publicly throughout the year. Before writing your self-evaluation, spend ten minutes reviewing your Karma profile — the kudos you’ve received, the values they were tied to, the moments colleagues called out. It’s often the most accurate account of what you actually contributed, written by the people who worked alongside you.

This is also useful evidence to reference in the self-evaluation itself. “I received 12 peer recognition messages this year specifically related to cross-team collaboration, which reflects the work I’ve invested in building relationships outside my immediate team” is more credible than “I am collaborative” because it’s sourced from observable behaviour rather than self-reported personality.

If your team doesn’t currently have a peer recognition system, the self-evaluation season is a good time to introduce one — because the problem of “I don’t know what to write about my colleagues for their 360 reviews” and “I don’t know what to write about myself for my self-evaluation” are both solved by having a continuous record of genuine peer appreciation throughout the year rather than trying to reconstruct it retrospectively.

Stas Kulesh
Stas Kulesh
Written by Stas Kulesh
LinkedIn
Founder of Karma and of Sliday, the Auckland design/dev shop behind it. I write most of this blog — posts on employee recognition, team culture, remote work, and the quiet behaviours that make teams perform. Off-keyboard: fretless guitar, Peep Show reruns, parenting.