Self review examples for designers
Read as influence on users and the organization — research that changed direction, systems that sped teams up, flows that moved a metric. Not a pile of screenshots.
A designer's self review should read as influence on users and the organization — research that changed direction, systems that sped teams up, flows that moved a metric. As a designer myself, I know the trap: our impact is real but easy to lose in a pile of screenshots.
Example lines
"Reduced onboarding drop-off through a redesigned first-run flow."
"Built components now adopted across three teams, cutting their build time."
"Ran the research that killed a costly feature before it shipped."
"Established the accessibility patterns the whole product now follows."
What to include — and what to cut
- User outcomes you moved — drop-off, conversion, task success
- Design-system adoption and the time it saved teams
- Research that changed a decision or roadmap
- Your specific contribution to shared work
- A tour of screens and Figma files
- "Made it look better" with no outcome
- Output counts — number of mockups
- Process described for its own sake
How to prioritize
- User and business outcomes first.
- System leverage second — adoption and time saved.
- Research influence third — decisions you changed.
- Craft and process last, as supporting evidence.
Name it or lose it
Design impact travels through other people, so it has to be named to exist. "Standardized the review criteria now used by the whole design org" is senior-level; "did design reviews" is not. For shared wins, state your part plainly.
How Workfied helps here
Workfied captures your design outcomes in your own words the day they land, so your review reads as impact instead of a portfolio tour. Built for you, never visible to your manager. Encrypted in transit and at rest.
Evidence
Include vs cut
Cut the screenshot reel. Keep the outcomes, the adoption, and the decisions your research changed.
Workfied house view
The trap
You speed up other teams and nobody attributes it. Named, it's seniority; unnamed, it's invisible.
Design practice
What to capture
The roadmap your research redirected and the costly feature you killed are your strongest, least-visible wins.
Workfied house view