Example Achievement Log for a UI Designer

A year in the life of a UI Designer's log

• Feb - task: Took over Booking flow redesign from departing designer mid-sprint. Picked up Figma file with three competing directions and no research backing. Started fresh audit of current drop-off rates at each step.
• Mar - achievement: Completed user testing on Booking flow with 12 participants. Found that date-picker modal was blocking 34% from completing first attempt. Redesigned as inline calendar with sticky summary panel.
• Apr - feedback: Product Lead said in standup: 'The research changed my mind. I was ready to ship the old version.' Showed up because I had clips and actual quotes, not hunches.
• Apr - task: Started color system audit across 40+ screens. Found 23 shades of grey doing the same job. Pushed back on Marketing's request to add brand gradients to UI, citing WCAG contrast failures.
• Jun - achievement: Published redesigned color palette: 8 functional greys, 4 semantic colors, documented contrast ratios. Migrated 18 core flows in Figma. QA caught zero color contrast regressions on staging.
• Jul - feedback: Engineering Lead said in code review: 'Your token names actually match what we're building. That's never happened before.' System cut theme-switching implementation time by 60%.
• Jul - achievement: Designed and coded interactive component library documentation in Storybook. Included 14 state variants for form inputs. Shipped with copy guidelines written with Content Designer.
• Sep - task: Designed new Settings page. UX researcher said the current one had 47% task failure rate. Iterated through five prototypes with her feedback. Final version scored 92%.
• Oct - achievement: Redesigned onboarding flow end-to-end. Mobile conversion rate went from 18% to 31%. Android version took longer; had to audit touch target spacing on small screens.
• Oct - task: Built component audit toolkit: spreadsheet tracking which screens use which variants. Found 6 undocumented button states still in production. Flagged for cleanup.
• Dec - feedback: Design Manager in one-on-one: 'You pushed back on the API proposal and were right. You saved us from shipping something that broke mobile.' Showed confidence in saying no.

What makes a strong entry

How this becomes your review in November

I redesigned the Booking flow from scratch after taking it over mid-sprint, running user testing that uncovered a date-picker modal blocking 34% of first attempts. I rebuilt it as an inline calendar with a sticky summary, and the Product Lead told me the research changed her mind about the old direction. I audited the color system across 40+ screens, published a palette of 8 functional greys and 4 semantic colors with documented contrast ratios, and migrated 18 core flows to the new tokens. QA caught zero color contrast regressions on staging, and the Engineering Lead said my token names actually matched what they were building. Over the course of the year, I designed the Settings page (which improved task success from 47% to 92%), end-to-end onboarding (which lifted mobile conversion from 18% to 31%), and a component library in Storybook with 14 form input variants. I also pushed back on requests that would have created problems, gradients breaking WCAG and an API proposal that would have broken mobile, and in both cases, that pushed back proved right.

Starting your own log

Don't try to reconstruct a year you have already had. Start from today, one line whenever something happens, and let it build. The Perform Review Achievement Log does this for you and can capture wins straight from Slack, and how to start an achievement log covers the wider playbook.

Example Logs for Related Roles

• Product Designer achievement log example
• Web Designer achievement log example
• UX Designer achievement log example
• Motion Designer achievement log example
• Graphic Designer achievement log example
• UX Researcher achievement log example