UX Designer Self-Evaluation Examples (Copy & Paste)
Reviewers can see your screens, but not the decisions behind them or what changed after launch. A strong self-evaluation connects your design work to user and business outcomes.
Below are 25 examples you can copy, grouped by what reviewers look for. Replace every [bracketed] value with your own numbers.
The formula behind every strong example
What you did
The action you personally took, not what the team did around you.
The measurable result
A number, a before-and-after, or a date. An honest estimate is fine.
Why it mattered
The effect on customers, revenue, the team, or a company goal.
Example: Lifted checkout completion from 61% to 74% (result) by redesigning the flow after testing it with 12 users (what I did), which became one of the biggest revenue wins of the quarter (why it mattered).
What reviewers look for in a ux designer self-evaluation
| Area | The question behind it |
|---|---|
| Research and insight | Did your research change what the team built? |
| Usability and product impact | Did your designs measurably improve the product for users and the business? |
| Design systems and craft | Did you make the whole team faster and the product more consistent? |
| Collaboration with engineering and product | Do features ship the way they were designed, with fewer surprises? |
| Influence and leadership | Do your ideas shape decisions beyond your own projects? |
25 self-evaluation examples for ux designers
Research and insight
- Ran [15] user interviews and [3] usability studies that shaped the roadmap for [feature].
- Synthesized [200]+ support tickets into [5] key pain points, [3] of which the team fixed this year.
- Set up a monthly research panel of [40] customers, cutting recruiting time from [2] weeks to [3] days.
- Ran a card-sorting study that guided our new navigation and cut "can't find" support tickets by [30]%.
- Started a monthly research readout that [3] product teams now attend.
Usability and product impact
- Redesigned checkout after usability testing, lifting completion from [61]% to [74]%.
- Simplified onboarding from [7] steps to [4], raising activation by [18]%.
- Reduced task time for [core workflow] by [40]%, measured in before-and-after testing.
- Designed [feature], which reached [35]% adoption within [2] months of launch.
- Fixed [12] accessibility issues, bringing our core flows to WCAG [2.2] AA.
Design systems and craft
- Built [40] reusable components in our design system, cutting design time for new screens by about [30]%.
- Documented usage guidelines for every component, so engineers needed fewer design check-ins.
- Unified [3] inconsistent button and form styles across the product.
- Created a dark mode theme for the design system that shipped across [4] products.
- Led a visual refresh of the marketing site that increased demo requests by [20]%.
Collaboration with engineering and product
- Paired with engineers during the build of [5] features, catching design issues before QA.
- Delivered specs covering edge cases and empty states, which cut design-related bugs by about half.
- Ran [4] design sprints with product and engineering to scope new features.
- Agreed success metrics with the PM for every feature I designed this year.
- Started a weekly design critique that [8] designers and PMs attend.
Influence and leadership
- Presented [3] design proposals to leadership, and [2] were funded for next year.
- Mentored [2] junior designers through their first end-to-end projects.
- Changed the direction of a planned feature by sharing test results, saving an estimated [6] weeks of engineering work.
- Wrote a set of design principles that the team uses to settle debates quickly.
- Interviewed [10] design candidates and helped hire [2].
Examples for a year that didn't go to plan
Most review forms ask about areas for growth. Name what happened, what you learned, and what you are changing.
- I sometimes polished designs before validating the idea. Next year I will test low-fidelity prototypes with at least [5] users before any high-fidelity work.
- I didn't always connect my work to business metrics. I now agree on a success metric with the PM before starting each project.
- I want to work faster with engineers, so I plan to learn [CSS layout and our component code].
- I found it hard to push back on rushed timelines. I now propose a scoped-down option instead of simply accepting or refusing.
- I want to present my work more often, so I plan to share one design case study with the wider company each quarter.
Before and after: vague vs. specific
"I designed the new checkout."
"I redesigned checkout after testing it with 12 users, lifting completion from 61% to 74%."
Why it works: It shows the method and the outcome, not just the deliverable.
"I worked on the design system."
"I built 40 reusable components that cut design time for new screens by about 30%."
Why it works: It turns infrastructure work into a team-wide speed-up.
"I did user research."
"I ran 15 interviews that identified 5 pain points, and the team fixed 3 of them this year."
Why it works: Research matters in a review when it changed what got built.
Free ux designer self-evaluation template
# [Your Name] — Self-Evaluation ([Review period])
Role: UX Designer · Team: [Team] · Manager: [Name]
## 1. Summary
The one or two results you most want your manager to remember.
## 2. Key accomplishments
Formula: what I did + the measurable result + why it mattered.
### Research and insight
-
### Usability and product impact
-
### Design systems and craft
-
### Collaboration with engineering and product
-
### Influence and leadership
-
## 3. Areas for growth
- What didn't go to plan, what I learned, and what I'm changing:
## 4. Goals for next period
- Write down what you remember. WinStash does the rest.
Paste rough notes about your year, even half-remembered ones. WinStash turns them into review-ready accomplishments in the same format as the examples above. Then log a one-minute note each Friday, and next year's review writes itself.
- Weekly updates for your manager
- Brag sheet for your review
- STAR stories for interviews
Frequently Asked Questions
What should a UX designer include in a self-evaluation?
Show the outcome of your work, not just the screens. Include research insights, usability or conversion changes, design system contributions, and how you influenced product decisions.
How do I show impact without analytics?
Use usability test results, task time, error rates, support ticket trends, or qualitative feedback. Before-and-after comparisons work even with small samples.
Should I link to my designs?
Yes, if your review tool allows it. Link the final design or a short case study next to each accomplishment so reviewers can see the work.
How do I take credit for team work?
Name your specific part: the research you ran, the decision you drove, or the design you owned. Credit collaborators by role.
How do I remember what I worked on all year?
Look back through your design files, research notes, and release notes. Next year, a quick Friday note on what changed and why keeps your evidence ready.